WebCodecs
In progress
This specification defines interfaces to codecs for encoding and decoding of audio and video.
This specification does not specify or require any particular codec or method of encoding or decoding. The purpose of this specification is to provide JavaScript interfaces to implementations of existing codec technology developed elsewhere. Implementers may support any combination of codecs or none at all.
Editors
Chris Cunningham, Paul Adenot, Bernard Aboba.
Media Working Group- Family:
- WebCodecs
This registration is entered into the [webcodecs-codec-registry]. It describes, for AVC (H.264), the (1) fully qualified codec strings, (2) the VideoDecoderConfig.description bytes, and (3) the codec-specific extensions to the VideoEncoderConfig.
The registration is not intended to include any information on whether a codec format is encumbered by intellectual property claims. Implementers and authors are advised to seek appropriate legal counsel in this matter if they intend to implement or use a specific codec format. Implementers of WebCodecs are not required to support the AVC / H.264 codec.
Editors
Chris Cunningham, Paul Adenot, Bernard Aboba.
Media Working Group- Family:
- WebCodecs
Miniapp
In progress
This specification is a registry of supplementary members for the Web Application Manifest and the Web App Manifest - Application Information specifications that provide additional metadata to an application manifest to describe MiniApps. This JSON-based manifest file enables developers to set up basic information, window style, page route, and other information of a MiniApp. The manifest also includes information about the window style like the navigation bar, title, window background color, page routing information, and the widgets that are part of a MiniApp.
Editors
Martin Alvarez-Espinar, Yongjing ZHANG.
MiniApps Working Group- Family:
- Miniapp
CSP
Complete
This document defines a policy language used to declare a set of content restrictions for a web resource, and a mechanism for transmitting the policy from a server to a client where the policy is enforced.
Editors
Mike West, Adam Barth, Daniel Veditz.
Web Application Security Working Group- Family:
- CSP
In progress
This document defines a mechanism by which web developers can control the resources which a particular page can fetch or execute, as well as a number of security-relevant policy decisions.
Editors
Mike West.
Web Application Security Working Group- Family:
- CSP
This document defines a mechanism by which a web page can embed a nested browsing context if and only if it agrees to enforce a particular set of restrictions upon itself.
Web Application Security Working Group- Family:
- CSP
DID
Complete
This document serves as an official registry for all known global parameters, properties, and values used by the Decentralized Identifier ecosystem.
Editors
Orie Steele, Manu Sporny.
Decentralized Identifier Working Group- Family:
- DID
This document sets out use cases and requirements for a new type of identifier.
Editors
Joe Andrieu, Phil Archer, Kim Duffy, Ryan Grant, Adrian Gropper.
Decentralized Identifier Working Group- Family:
- DID
In progress
This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent.
Editors
Drummond Reed, Manu Sporny, Markus Sabadello, Dave Longley, Christopher Allen.
Decentralized Identifier Working Group- Family:
- DID
Web Audio API
Complete
This document introduces a series of scenarios and a list of requirements guiding the work of the W3C Audio Working Group in its development of a web API for processing and synthesis of audio on the web.
Editors
Joe Berkovitz, Olivier Thereaux.
Audio Working Group- Family:
- Web Audio API
In progress
This specification describes a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported.
Editors
Paul Adenot, Hongchan Choi.
Audio Working Group- Family:
- Web Audio API
Picture-in-Picture
In progress
This specification intends to provide APIs to allow websites to create a floating video window always on top of other windows so that users may continue consuming media while they interact with other content sites, or applications on their device.
Editors
Francois Beaufort, Mounir Lamouri.
Media Working Group- Family:
- Picture-in-Picture
WebTransport
In progress
This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received between a browser and server, utilizing [WEB-TRANSPORT-HTTP3]. This specification is being developed in conjunction with a protocol specification developed by the IETF WEBTRANS Working Group.
Editors
Bernard Aboba, Victor Vasiliev, Yutaka Hirano.
WebTransport Working Group- Family:
- WebTransport
Media Session Standard
In progress
This specification enables web developers to show customized media metadata on platform UI, customize available platform media controls, and access platform media keys such as hardware keys found on keyboards, headsets, remote controls, and software keys found in notification areas and on lock screens of mobile devices.
Editors
Mounir Lamouri, Becca Hughes.
Media Working Group- Family:
- Media Session Standard
DCAT
Complete
DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.
Editors
Riccardo Albertoni, David Browning, Simon Cox, Alejandra Gonzalez Beltran, Andrea Perego, Peter Winstanley.
Dataset Exchange Working Group- Family:
- DCAT
Available in:
日本語In progress
DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.
Editors
Riccardo Albertoni, David Browning, Simon Cox, Alejandra Gonzalez Beltran, Andrea Perego, Peter Winstanley.
Dataset Exchange Working Group- Family:
- DCAT
WAI-ARIA
Complete
Recommends approaches for developers of rich internet applications to make widgets, navigation, and behaviors accessible using WAI-ARIA 1.1 roles, states, and properties.
Editors
Matthew King, JaEun Jemma Ku, James Nurthen, Zoë Bijl, Michael Cooper, Joseph Scheuhammer, Lisa Pappas, Richard Schwerdtfeger.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs.
Editors
Joanmarie Diggs, Bryan Garaventa, Michael Cooper.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Defines how user agents map the WAI-ARIA Graphics Module markup to platform accessibility APIs.
Editors
Amelia Bellamy-Royds, Joanmarie Diggs, Michael Cooper.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Defines a WAI-ARIA module of core roles, states and properties specific to web graphics. These semantics allow an author to express the logical structure of the graphic to assistive technologies, allowing assistive technologies to provide semantic navigation and adapt styling and interactive features.
Editors
Amelia Bellamy-Royds, Joanmarie Diggs, Michael Cooper.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Accessibility of web content requires semantic information about widgets, structures and behaviors in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification defines a module encompassing an ontology of roles, states and properties specific to the digital publishing industry. These semantics are designed to allow an author to convey user interface behaviors and structural information to assistive technologies and to enable semantic navigation, styling and interactive features used by readers.
Editors
Matt Garrish, Tzviya Siegman, Markus Gylling, Shane McCarron.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Describes how user agents should expose semantics of web content languages to various accessibility APIs in an interoperable manner. This helps users with disabilities to obtain and interact with information using assistive technologies. This specification defines core functionality; other specifications depend on and extend this for specific technologies.
Editors
Joanmarie Diggs, Joseph Scheuhammer, Richard Schwerdtfeger, Michael Cooper, Andi Snow-Weaver, Aaron Leventhal.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Defines how user agents map the Digital Publishing WAI-ARIA Module markup to platform accessibility application programming interfaces (APIs). It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.
Editors
Richard Schwerdtfeger, Joanmarie Diggs.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Recommends approaches for developers of rich internet applications to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. WAI-ARIA 1.1 adds features new since WAI-ARIA 1.0 to complete the HTML + ARIA accessibility model. It is expected this will complement HTML 5.1.
Editors
Joanmarie Diggs, Shane McCarron, Michael Cooper, Richard Schwerdtfeger, James Craig.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Available in:
日本語Describes how user agents should support keyboard navigation, respond to roles, states, and properties provided in Web content via WAI-ARIA, and expose this to accessibility APIs.
Editors
Joseph Scheuhammer, Michael Cooper.
Protocols and Formats Working Group- Family:
- WAI-ARIA
Accessibility of Web content to people with disabilities requires semantic information about widgets, structures, and behaviors, in order to allow Assistive Technologies to make appropriate transformations. This specification provides an ontology of roles, states, and properties that set out an abstract model for accessible interfaces and can be used to improve the accessibility and interoperability of Web Content and Applications. This information can be mapped to accessibility frameworks that use this information to provide alternative access solutions. Similarly, this information can be used to change the rendering of content dynamically using different style sheet properties. The result is an interoperable method for associating behaviors with document-level markup. This document is part of the WAI-ARIA suite described in the ARIA Overview.
Editors
James Craig, Michael Cooper.
Protocols and Formats Working Group- Family:
- WAI-ARIA
The Role Attribute defined in this specification allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element.
Editors
Shane McCarron.
Protocols and Formats Working Group- Family:
- WAI-ARIA
Available in:
한국어In progress
This specification defines the web developer rules (author conformance requirements) for the use of WAI ARIA attributes on HTML elements. It also defines requirements for Conformance Checking tools.
Editors
Steve Faulkner, Scott O'Hara, Patrick Lauke.
Web Applications Working Group- Family:
- WAI-ARIA
Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user interface behaviors and structural information to assistive technologies in document-level markup. This version adds features new since WAI-ARIA 1.1 [wai-aria-1.1] to improve interoperability with assistive technologies to form a more consistent accessibility model for [HTML] and [SVG2]. This specification complements both [HTML] and [SVG2].
This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.
Editors
Joanmarie Diggs, James Nurthen, Michael Cooper.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Defines how user agents map HTML 5.1 elements and attributes to platform accessibility APIs. This promotes interoperable exposure of roles, states, properties, and events and helps to ensure that this information appears in a manner consistent with author intent.
Editors
Steve Faulkner, Alexander Surkov, Scott O'Hara, Bogdan Brinza, Jason Kiss, Cynthia Shelly.
Web Applications Working Group- Family:
- WAI-ARIA
Recommends approaches for developers of rich internet applications to make widgets, navigation, and behaviors accessible using WAI-ARIA 1.1 roles, states, and properties. ARIA Practices 1.2 provides additional authoring guidance for new features in WAI-ARIA 1.2.
Editors
Matthew King, JaEun Jemma Ku, James Nurthen, Zoë Bijl, Michael Cooper, Joseph Scheuhammer, Lisa Pappas, Richard Schwerdtfeger.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
Describes how user agents should expose semantics of web content languages to various accessibility APIs in an interoperable manner. This helps users with disabilities to obtain and interact with information using assistive technologies. Core-AAM 1.2 provides additional mapping information for new features in WAI-ARIA 1.2.
Editors
Joanmarie Diggs, Michael Cooper, Richard Schwerdtfeger, Joseph Scheuhammer, Andi Snow-Weaver, Aaron Leventhal, Melanie Richards, James Craig, Alexander Surkov.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
This document describes how user agents determine the names and descriptions of accessible objects from web content languages. This information is in turn exposed through accessibility APIs so that assistive technologies can identify these objects and present their names or descriptions to users. Documenting the algorithm through which names and descriptions are to be determined promotes interoperable exposure of these properties among different accessibility APIs and helps to ensure that this information appears in a manner consistent with author intent.
Editors
Bryan Garaventa, Joanmarie Diggs, Michael Cooper.
Accessible Rich Internet Applications Working Group- Family:
- WAI-ARIA
This document is a practical guide for developers on how to add accessibility information to HTML elements using ARIA, a markup mechanism for making Web content and Web applications more accessible to people with disabilities.
Editors
Steve Faulkner, David MacDonald.
Web Platform Working Group- Family:
- WAI-ARIA
Describes how user agents map SVG markup to platform accessibility APIs. When user agents support this specification, SVG authors can create accessible rich internet applications, including charts, graphs, and other drawings.
Editors
Amelia Bellamy-Royds, Ian Pouncey.
SVG Working Group- Family:
- WAI-ARIA
The Roadmap for Accessible Rich Internet Applications addresses the accessibility of dynamic Web content for people with disabilities. The roadmap introduces the technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for Rich Internet Applications. The roadmap also describes new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures. These new technologies can be used to improve the accessibility and usability of Web resources by people with disabilities, without extensive modification to existing libraries of Web resources. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.
Editors
Richard Schwerdtfeger.
Protocols and Formats Working Group- Family:
- WAI-ARIA
TBD
Complete
This document is a gap analysis and roadmap for the state of accessibility for people with learning and cognitive disabilities when using the Web and information technologies. It builds on the information presented in Cognitive Accessibility User Research and Cognitive Accessibility Issue Papers to evaluate where user needs remain to be met in technologies and accessibility guidelines. For various accessibility issues, this document provides a summary of issues and techniques, then identifies gaps and unmet user needs and suggest ways to meet these needs.
Editors
Lisa Seeman-Horwitz, Rachael Bradley Montgomery, Steve Lee, Ruoxi Ran.
Accessibility Guidelines Working GroupAccessible Platform Architectures Working Group
- Family:
- TBD
The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware agnostic pointer input from devices including a mouse, pen, touchscreen, etc. For compatibility with existing mouse based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.
Editors
Matt Brubeck, Rick Byers, Patrick Lauke, Navid Zolghadr.
Pointer Events Working Group- Family:
- TBD
Available in:
日本語In progress
This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.
Editors
Jeff Hodges, J.C. Jones, Michael Jones, Akshay Kumar, Emil Lundberg.
Web Authentication Working Group- Family:
- TBD
This registry is intended to enhance interoperability among implementations and users of [WEBCODECS]. In particular, this registry provides the means to identify and avoid collisions among codec strings and provides a mechanism to define codec-specific members of [WEBCODECS] codec configuration dictionaries.
This registry is not intended to include any information on whether a codec format is encumbered by intellectual property claims. Implementers and users are advised to seek appropriate legal counsel in this matter if they intend to implement or use a specific codec format. Implementers of WebCodecs are not required to support any particular codec nor registry entry.
Editors
Chris Cunningham, Paul Adenot, Bernard Aboba.
Media Working Group- Family:
- TBD
This CSS module describes how to collate style rules and assign values to all properties on all elements. By way of cascading and inheritance, values are propagated for all properties on all elements.
Editors
Elika Etemad, Miriam Suzanne, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- TBD
The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware agnostic pointer input from devices including a mouse, pen, touchscreen, etc. For compatibility with existing mouse based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.
Editors
Patrick Lauke, Navid Zolghadr, Matt Brubeck, Rick Byers.
Pointer Events Working Group- Family:
- TBD
This specification defines an API for specifying privacy and integrity policies on data, in the form of origin labels, and a mechanism for confining code according to such policies. This allows Web application authors and server operators to shared data with untrusted - buggy but not malicious - code (e.g., in a mashup scenario) yet impose restrictions on how the code can share the data further.
Editors
Deian Stefan.
Web Application Security Working Group- Family:
- TBD
This specification introduces and compares two client-side APIs for processing and synthesizing real-time audio streams in the browser.
Editors
Robert O'Callahan, Chris Rogers.
Audio Working Group- Family:
- TBD
The Points of Interest Core describes a data model and XML syntax for representing information about points of interest on the World Wide Web.
Editors
Matt Womer.
Points of Interest Working Group- Family:
- TBD
Web Payments
Complete
Merchant validation is the process by which a payment handler validates the identity of a merchant against some value (usually some cryptographic challenge response). Validated merchants are allowed to interface with a payment handler. Details of how actual validation is performed is outside the scope of this specification.
Editors
Marcos Caceres.
Web Payments Working Group- Family:
- Web Payments
EMVCo, FIDO Alliance and W3C have all taken steps to improve online payment security through the development of interoperable technical specifications. In this document we describe the core capabilities provided by some of their specifications, what problems can be solved by combining them, and potential changes to improve how they work together.
Editors
Ian Jacobs.
Web Payment Security Interest Group- Family:
- Web Payments
This document outlines the W3C Web Payments ecosystem by introducing readers to the goals of the ecosystem, messages, roles, and information flow in the system.
Editors
Manu Sporny, Adrian Hope-Bailie, Nick Telford-Reed, Roy McElmurry, Dapeng Liu.
Web Payments Working Group- Family:
- Web Payments
In progress
The Payment Request API provides a standard way to initiate payment requests from Web pages and applications. User agents implementing that API prompt the user to select a way to handle the payment request, after which the user agent returns a payment response to the originating site. This specification defines capabilities that enable Web applications to handle payment requests.
Editors
Adrian Hope-Bailie, Jason Normore, Ian Jacobs, Rouslan Solomakhin, Jinho Bang, Tommy Thorsen, Adam Roach.
Web Payments Working Group- Family:
- Web Payments
The Basic Card Payment specification describes the data formats used by the PaymentRequest API to support payment by payment cards such as credit or debit cards.
Editors
Marcos Caceres, Domenic Denicola, Zach Koch, Roy McElmurry, Adrian Bateman.
Web Payments Working Group- Family:
- Web Payments
The Payment Request API requires that merchants supply a list of identifiers for supported payment methods. This document defines those identifier strings and how they are created.
Editors
Marcos Caceres, Domenic Denicola, Zach Koch, Roy McElmurry.
Web Payments Working Group- Family:
- Web Payments
This specification defines the machine-readable manifest file, known as a payment method manifest, describing how a payment method participates in the Web Payments ecosystem, and how such files are to be used.
Editors
Dapeng Liu, Domenic Denicola, Zach Koch.
Web Payments Working Group- Family:
- Web Payments
File API
In progress
This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data.
Editors
Marijn Kruisselbrink, Arun Ranganathan.
Web Applications Working Group- Family:
- File API
Image Resource
In progress
This document defines the concept of an "image resource" and a corresponding WebIDL ImageResource dictionary. Web APIs can use the ImageResource dictionary to represent an image resource in contexts where an HTMLImageElement is not suitable or available (e.g., in a Worker).
Editors
Aaron Gustafson, Rayan Kanso, Marcos Caceres.
Web Applications Working Group- Family:
- Image Resource
CSS Text
In progress
This CSS module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
Editors
Elika Etemad, Koji Ishii, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Text
This module defines properties for text manipulation and specifies their processing model. It covers line breaking, justification and alignment, white space handling, and text transformation.
Editors
Elika Etemad, Koji Ishii, Alan Stearns, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Text
Performance instrumentation
Complete
This specification defines a JavaScript interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.
Editors
Ilya Grigorik.
Web Performance Working Group- Family:
- Performance instrumentation
This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
Editors
Ilya Grigorik.
Web Performance Working Group- Family:
- Performance instrumentation
This specification defines an interface for web applications to access timing information related to navigation and elements. It is used by other specifications, like User Timing.
Editors
Jatinder Mann, Zhiheng Wang.
Web Performance Working Group- Family:
- Performance instrumentation
This document provides an interface for web applications to access timing information related to navigation and elements.
Editors
Zhiheng Wang.
Web Performance Working Group- Family:
- Performance instrumentation
In progress
This specification defines an interface for web applications to access the complete timing information for resources in a document.
Editors
Yoav Weiss, Noam Rosenthal, Ilya Grigorik, Todd Reifsteck, Arvind Jain, Jatinder Mann, Zhiheng Wang, Anderson Quach.
Web Performance Working Group- Family:
- Performance instrumentation
This specification defines an API that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.
Editors
Yoav Weiss, Ilya Grigorik, James Simonsen, Jatinder Mann.
Web Performance Working Group- Family:
- Performance instrumentation
This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.
Editors
Nicolas Pena Moreno, Ilya Grigorik, Jatinder Mann, Zhiheng Wang, Anderson Quach.
Web Performance Working Group- Family:
- Performance instrumentation
This document provides an interface for web applications to access timing information related to navigation and elements.
Editors
Yoav Weiss, Ilya Grigorik, Tobin Titus, Jatinder Mann, Arvind Jain.
Web Performance Working Group- Family:
- Performance instrumentation
Server Timing, part of the performance timeline metrics, provides API access to request-response cycle performance metrics communicated from the server to the user agent.
Editors
Charles Vazac, Ilya Grigorik.
Web Performance Working Group- Family:
- Performance instrumentation
This specification extends the High Resolution Time specification by providing methods to store and retrieve high resolution performance metric data.
Editors
Ilya Grigorik.
Web Performance Working Group- Family:
- Performance instrumentation
This registry is intended to provide a central location for enumerating identified interface types of PerformanceEntry objects, which contain various data metrics for the the full lifecycle of a web application.
Editors
Philippe Le Hégaret.
Web Performance Working Group- Family:
- Performance instrumentation
The reporting API provides a generic reporting framework which allows Web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.
Editors
Douglas Creager, Ilya Grigorik, Paul Meyer, Mike West.
Web Performance Working Group- Family:
- Performance instrumentation
This document defines an API that can be used to capture a series of key moments (First Paint, First Contentful Paint) during pageload which developers care about.
Editors
Shubhie Panicker.
Web Performance Working Group- Family:
- Performance instrumentation
This specification defines an interface for web applications to access timing information related to HTML elements.
Editors
Arvind Jain, Todd Reifsteck, Jatinder Mann, Zhiheng Wang, Anderson Quach.
Web Performance Working Group- Family:
- Performance instrumentation
Media Capture
In progress
This document defines a set of APIs that allow local media, including audio and video, to be requested from a platform, media to be sent over the network to another browser or device implementing the appropriate set of real-time protocols, and media received from another browser or device to be processed and displayed locally.
Editors
Cullen Jennings, Bernard Aboba, Jan-Ivar Bruaroey, Henrik Boström, youenn fablet, Daniel Burnett, Adam Bergkvist, Anant Narayanan.
Web Real-Time Communications Working Group- Family:
- Media Capture
This document specifies methods and camera settings to produce photographic image capture. The source of images is, or can be referenced via a MediaStreamTrack.
Editors
Miguel Casas-sanchez, Rijubrata Bhaumik, Giridhar Mandyam.
Web Real-Time Communications Working Group- Family:
- Media Capture
The Open Screen Protocol is a suite of network protocols that allow user agents to implement the Presentation API and the Remote Playback API in an interoperable fashion.
Editors
Mark Foltz.
Second Screen Working Group- Family:
- Media Capture
This document defines a recording API for use with MediaStreams.
Editors
Miguel Casas-sanchez, James Barnett, Travis Leithead.
Web Real-Time Communications Working Group- Family:
- Media Capture
This document defines how a user's display, or parts thereof, can be used as the source of a media stream using getOutputMedia, an extension to the Media Capture API [GETUSERMEDIA].
Editors
Martin Thomson, Keith Griffin, Suhas Nandakumar, Henrik Boström, Jan-Ivar Bruaroey.
Web Real-Time Communications Working Group- Family:
- Media Capture
This specification extends MediaStreamTrack to provide a media-content hint attribute. This optional hint permits MediaStreamTrack consumers such as PeerConnection or MediaRecorder to encode or process track media with methods more appropriate to the type of content that is being consumed.
Editors
Harald Alvestrand.
Web Real-Time Communications Working Group- Family:
- Media Capture
This document defines how a stream of media can be captured from a DOM
element, such as a <video>, <audio>,
or <canvas> element, in the form of
a MediaStream.
Editors
Martin Thomson, Miguel Casas-sanchez, Emircan Uysaler.
Web Real-Time Communications Working Group- Family:
- Media Capture
This specification extends the Media Capture and Streams specification to allow a depth stream to be requested from 3D cameras.
Editors
Anssi Kostiainen, Ningxin Hu, Aleksandar Stojiljkovic, Rob Manson.
Devices and Sensors Working GroupWeb Real-Time Communications Working Group
- Family:
- Media Capture
This document collates the scenarios that are target use cases for the Media Capture API that enables access to media input capabilities for Web applications using Javascript.
Editors
Travis Leithead.
Devices and Sensors Working GroupWeb Real-Time Communications Working Group
- Family:
- Media Capture
Gamepad
In progress
Defines a low-level interface that represents gamepad devices.
Editors
Steve Agoston, James Hollyer, Matthew Reynolds, Brandon Jones, Scott Graham, Theodore Mielczarek.
Web Applications Working Group- Family:
- Gamepad
Web Authentication
Complete
This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.
Editors
Jeff Hodges, J.C. Jones, Michael Jones, Akshay Kumar, Emil Lundberg.
Web Authentication Working Group- Family:
- Web Authentication
This specification defines an API that enables web pages to access WebAuthn compliant strong cryptographic credentials through browser script.
Editors
Dirk Balfanz, Alexei Czeskis, Jeff Hodges, J.C. Jones, Michael Jones, Akshay Kumar, Huakai Liao, Rolf Lindemann, Emil Lundberg.
Web Authentication Working Group- Family:
- Web Authentication
Manifest
In progress
This specification defines a manifest, which provides developers with a centralized place to put metadata about a web application.
Editors
Marcos Caceres, Kenneth Christiansen, Mounir Lamouri, Anssi Kostiainen, Matt Giuca, Aaron Gustafson.
Web Applications Working Group- Family:
- Manifest
EPUB
Complete
EPUB Accessibility Techniques defines discovery and content accessibility requirements for EPUB Publications.
Editors
Matt Garrish, George Kerscher, Charles LaPierre, Gregorio Pellegrino, Avneesh Singh.
EPUB 3 Working Group- Family:
- EPUB
Available in:
日本語This document provides a starting point for content authors and software developers wishing to understand the EPUB® 3 specifications. It consists entirely of informative overview material that describes the features available in EPUB 3.
The current version of EPUB 3 is defined in [EPUB-33], which represents the second minor revision of the standard. The substantive changes since EPUB 3.2 [EPUB-32] are documented in a separate section in the EPUB 3.3 document itself.
Editors
Garth Conboy, Matt Garrish, Daniel Weck.
EPUB 3 Working Group- Family:
- EPUB
Available in:
日本語This specification, EPUB Multiple-Rendition Publications, defines the creation and rendering of EPUB® Publications consisting of more than one Rendition.
Editors
Matt Garrish.
EPUB 3 Working Group- Family:
- EPUB
In progress
EPUB® 3 defines a ../distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced Web content — including HTML, CSS, SVG and other resources — for distribution in a single-file container.
This specification defines the conformance requirements for EPUB® 3 Reading Systems — the user agents that render EPUB Publications.
Editors
Dave Cramer, Matt Garrish, Ivan Herman, Garth Conboy, Marisa DeMeglio, Daniel Weck.
EPUB 3 Working Group- Family:
- EPUB
EPUB® 3 defines a ../distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced Web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file container.
This specification defines the authoring requirements for EPUB Publications and represents the third major revision of the standard.
Editors
Matt Garrish, Ivan Herman, Dave Cramer, Garth Conboy, Marisa DeMeglio, Daniel Weck.
EPUB 3 Working Group- Family:
- EPUB
This document specifies content conformance requirements for verifying the accessibility of EPUB Publications. It also specifies accessibility metadata requirements for the discoverability of EPUB Publications.
Editors
Matt Garrish, George Kerscher, Charles LaPierre, Gregorio Pellegrino, Avneesh Singh.
EPUB 3 Working Group- Family:
- EPUB
CSS Easing Functions
In progress
This CSS module describes a way for authors to define a transformation to be applied to the time of an animation. This can be used to produce animations that mimic physical phenomena such as momentum or to cause the animation to move in discrete steps producing robot-like movement.
Editors
Brian Birtles, Dean Jackson, Matt Rakow, Shane Stephens.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Easing Functions
Language Gap Analysis
In progress
This document describes and prioritises gaps for the support of the Tamil script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of languages using the Bengali script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of the Devanagari script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Akshat Joshi, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of languages using the Thai script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of languages using the Gujarati script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Neha Gupta, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Adlam on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Arabic and Persian languages on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Shervin Afshar, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of N’Ko on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Hebrew on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of German on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of French on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Osage using the Osage script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders. This is a preliminary analysis.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Japanese on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of the Traditional Mongolian script (Hudum) on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Lao on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Dutch on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Bert Bos, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of languages using the Ethiopic script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Georgian on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Modern Greek on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Hungarian on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Ivan Herman, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Inuktitut & Cree using Canadian Syllabics on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Cherokee on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Khmer on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Javanese written with the Javanese script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Simplified and Traditional Chinese on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Fuqiao Xue, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of Tibetan on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document describes and prioritises gaps for the support of languages using the Gurmukhi script on the Web and in eBooks. In particular, it is concerned with text layout. It checks that needed features are supported in W3C specifications, in particular HTML and CSS and those relating to digital publications. It also checks whether the features have been implemented in browsers and ereaders.
Editors
Akshat Joshi, Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
This document points browser implementers and specification developers to information about how to support typographic features of scripts or writing systems from around the world, and also points to relevant information in specifications, to tests, and to useful articles and papers. It is not exhaustive, and will be added to from time to time.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Language Gap Analysis
Xquery & XSLT
Complete
This specification defines the syntax and semantics of XSLT 2.0, a language for transforming XML documents into other XML documents.
XSLT 2.0 is a revised version of the XSLT 1.0 Recommendation [XSLT 1.0] published on 16 November 1999.
XSLT 2.0 is designed to be used in conjunction with XPath 2.0, which is defined in [XPath 2.0]. XSLT shares the same data model as XPath 2.0, which is defined in [Data Model], and it uses the library of functions and operators defined in [Functions and Operators].
XSLT 2.0 also includes optional facilities to serialize the results of a transformation, by means of an interface to the serialization component described in [XSLT and XQuery Serialization].
This document contains hyperlinks to specific sections or definitions within other documents in this family of specifications. These links are indicated visually by a superscript identifying the target specification: for example XP for XPath, DM for the XDM data model, FO for Functions and Operators.
Editors
Michael Kay.
XSLT Working Group- Family:
- Xquery & XSLT
This document specifies goals and requirements for the XQuery Scripting Extension.
Editors
Daniel Engovatov, Daniela Florescu, Giorgio Ghelli.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies usage scenarios for the XQuery Scripting Extension.
Editors
John Snelson.
XML Query Working Group- Family:
- Xquery & XSLT
This specification defines the syntax and semantics of XSLT 3.0, a language for transforming XML documents into other XML documents.
Editors
Michael Kay.
XSLT Working Group- Family:
- Xquery & XSLT
XQueryX 3.1 defines an XML syntax for the semantics defined by XQuery 3.1.
Editors
Jim Melton, Josh Spiegel.
XML Query Working Group- Family:
- Xquery & XSLT
The XPath and XQuery Data Model (XDM) 3.1 defines the data model on which all operations of XPath 3.1, XQuery 3.1, and XSLT 3.1 operate.
Editors
Norman Walsh, John Snelson, Andrew Coleman.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
XPath and XQuery Functions and Operators 3.0 defines a library of functions available for use in XPath, XQuery, XSLT and other languages.
Editors
Michael Kay.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines serialization of an instance of the XQuery and XPath Data model Data Model into a sequence of octets, such as into XML, text, HTML, JSON.
Editors
Andrew Coleman, Michael Sperberg-McQueen.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
XQuery 3.1 is a versatile query and application development language, capable of processing the information content of diverse data sources including structured and semi-structured documents, relational databases and tree-bases databases. The XQuery language is designed to support powerful optimizations and pre-compilation leading to very efficient searches over large amounts of data, including over so-called XML-native databases that read and write XML but have an efficient internal storage.
Editors
Jonathan Robie, Michael Dyck, Josh Spiegel.
XML Query Working Group- Family:
- Xquery & XSLT
XPath is an expression language that allows the processing of values conforming to the data model defined in the XQuery and Xpath Data Model.
Editors
Jonathan Robie, Michael Dyck, Josh Spiegel.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility 3.0 provides expressions that can be used to make persistent changes to instances of the XQuery and XPath Data Model 3.0.
Editors
John Snelson, Jim Melton.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies goals, requirements and use cases for the XQuery Update Facility 3.0.
Editors
Andrew Coleman.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies goals and requirements for XQuery 3.1.
Editors
Jonathan Robie.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies requirements and use cases for Full-Text Search for use in XQuery 3.0 and XPath 3.0.
Editors
Pat Case.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines the syntax and formal semantics of XQuery and XPath Full Text 3.0, which is a language that extends XQuery 3.0 [XQuery 3.0: An XML Query Language] and XPath 3.0 [XML Path Language (XPath) 3.0] with full-text search capabilities.
Editors
Mary Holstege, Jim Melton.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This specification defines an extension to [XQuery 1.0] and [XQuery Update Facility]. Expressions can be evaluated in a specific order, with later expressions seeing the effects of the expressions that came before them. This specification introduces the concept of a block with local variable declarations, as well as several new kinds of expressions, including assignment, while, and exit expressions.
Editors
John Snelson, Don Chamberlin, Daniel Engovatov, Dana Florescu, Giorgio Ghelli, Jim Melton, Jerome Simeon.
XML Query Working Group- Family:
- Xquery & XSLT
XPath and XQuery Functions and Operators 3.0 (renamed from XPath and XQuery Functions and Operators 1.1 to align with the family of "3.0" specifications) defines a library of functions available for use in XPath 3.0, XQuery 3.0, and XSLT 3.0. Some of the new features since XPath 2.0 and XQuery 1.0 Functions and Operators include:
- More than 30 new functions have been added, including functions transferred from the XSLT 2.0 specification into Functions and Operators 3.0 and additional versions of existing functions with different signatures
- The syntax for regular expressions was enhanced to allow for non-capturing groups; additionally, a new flag value was added for regular-expression-related functions that accept a flag argument
- Support for function items has been added in the form of a number of new functions
- The description of fn:error was rewritten to accommodate the addition of try/catch capabilities in XQuery 3.0
Editors
Michael Kay.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
XSLT and XQuery Serialization 3.0 (renamed from XQueryX 1.1 to align with the family of "3.0" specifications) defines serialization of an instance of XDM 3.0 into a sequence of octets. Important new features in Serialization 3.0 include:
- Supports serialization of function items
- Adds a definition of a suppress-indentation serialization parameter
- Clarifies how minimized attributes, as well as the "script" and "style" elements, are handled under the rules of the HTML output method
Editors
Henry Zongaro, Andrew Coleman, Michael Sperberg-McQueen.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
The design of XQuery 3.0 was supported by use cases gathered following the XQuery 1.0 development timeframe. This Use Cases document (renamed from XQuery Use Cases 1.1 to align with the family of "3.0" specifications) corrects one Use Case.
Editors
Jonathan Robie, Tim Kraska.
XML Query Working Group- Family:
- Xquery & XSLT
XQuery 3.0 (renamed from XQuery 1.1 to align with the family of "3.0" specifications) is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. Important new features since XQuery 1.0 include:
- The "group by" clause, windowing ("tumbling window" and "sliding window"), the "count" clause, and the "allowing empty" clause in FLWOR expressions
- A try/catch capability to support application handling of errors
- Literal function items, inline functions, dynamic function invocations, and function item coercion
- Nondeterministic functions and private functions
- A value-based switch expression (analogous to the existing typeswitch expression)
- Computed namespace constructors
- Declaration of serialization parameters
- Support for new Functions and Operators 3.0 capabilities
- Cleaner definition of module import
Editors
Jonathan Robie, Don Chamberlin, Michael Dyck, John Snelson.
XML Query Working Group- Family:
- Xquery & XSLT
XPath 3.0 (renamed from XPath 2.1 to align with the family of "3.0" specifications) is an expression language that allows the processing of values conforming to the data model defined in [XQuery and XPath Data Model (XDM) 3.0]. Some of the important new features since XPath 2.0 are:
- Literal function items, inline functions, dynamic function invocations, and function item coercion
- Clarification of rules associated with sequence type matching
- let expressions
- EQNames (QNames with a namespace URI instead of a namespace prefix)
- Support for union types in casting and function arguments
Editors
Jonathan Robie, Don Chamberlin, Michael Dyck, John Snelson.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
XQueryX 3.0 (renamed from XQueryX 1.1 to align with the family of "3.0" specifications) defines an XML syntax for the semantics defined by XQuery 3.0. This publication is aligned with XQuery 3.0
Editors
Jim Melton.
XML Query Working Group- Family:
- Xquery & XSLT
The design of XQuery 3.0 was driven by requirements gathered following the XQuery 1.0 development timeframe. This Requirements document (renamed from XQuery Requirements 1.1 to align with the family of "3.0" specifications) provides an update on the status of each requirements.
Editors
Jonathan Robie, Daniel Engovatov.
XML Query Working Group- Family:
- Xquery & XSLT
XPath and XQuery Data Model (XDM) 3.0 (renamed from XPath and XQuery Functions and Operators (XDM) 1.1 to align with the family of "3.0" specifications) defines the data model on which all operations of XPath 3.0, XQuery 3.0, and XSLT 3.0 operate. In this version of XDM, two new data types have been added:
- From XML Schema 1.1 Part 2 (Datatypes), the xs:dateTimeStamp data type
- To support XPath 3.0's and XQuery 3.0's function item capabilities, a function item data type
Editors
Norman Walsh, Anders Berglund, John Snelson.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines the syntax and formal semantics of XQuery and XPath Full Text 1.0 which is a language that extends XQuery 1.0 [XQuery 1.0: An XML Query Language] and XPath 2.0 [XML Path Language (XPath) 2.0] with full-text search capabilities.
Editors
Pat Case, Michael Dyck, Mary Holstege, Sihem Amer-Yahia, Chavdar Botev, Stephen Buxton, Jochen Dörre, Jim Melton, Michael Rys, Jayavel Shanmugasundaram.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines an update facility that extends the XML Query language, XQuery. The XQuery Update Facility provides expressions that can be used to make persistent changes to instances of the XQuery 1.0 and XPath 2.0 Data Model.
Editors
Don Chamberlin, Jonathan Robie, Michael Dyck, Daniela Florescu, Jim Melton, Jerome Simeon.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies usage scenarios for the XQuery Update Facility.
Editors
Ioana Manolescu, Jonathan Robie.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies goals and requirements for the XQuery Update Facility.
Editors
Don Chamberlin, Jonathan Robie.
XML Query Working Group- Family:
- Xquery & XSLT
The document specifies requirements for Full-Text Search for use in XQuery [XQuery] and XPath [XPath].
Editors
Stephen Buxton, Pat Case, Michael Rys.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document specifies usage scenarios for full-text queries as part of XML Query [XQuery 1.0: An XML Query Language] and XPath [XML Path Language (XPath) 2.0].
Editors
Pat Case, Sihem Amer-Yahia.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines formally the semantics of XQuery 1.0 [XQuery 1.0: An XML Query Language] and XPath 2.0 [XML Path Language (XPath) 2.0].
Editors
Denise Draper, Michael Dyck, Peter Fankhauser, Mary Fernandez, Ashok Malhotra, Kristoffer Rose, Michael Rys, Jerome Simeon, Philip Wadler.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
XQuery 1.1 fixes some bugs and adds some substantial new features to XQuery 1.0.
Editors
Scott Boag, Don Chamberlin, Mary Fernandez, Daniela Florescu, Jonathan Robie, Jerome Simeon.
XML Query Working Group- Family:
- Xquery & XSLT
XPath is a way to refer to parts of an XML document. XPath 2.0 is based on the XQuery 1.0 and XPath 2.0 Data Model (XDM), and also introduces Schema awareness and data typing.
Editors
Anders Berglund, Scott Boag, Don Chamberlin, Mary Fernandez, Michael Kay, Jonathan Robie, Jerome Simeon.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
XQueryX Second Edition.
Editors
Jim Melton, Subramanian Muralidhar.
XML Query Working Group- Family:
- Xquery & XSLT
This document defines the W3C XQuery 1.0 and XPath 2.0 Data Model (XDM), which is the data model of [XPath 2.0], [XSLT 2.0], and [XQuery], and any other specifications that reference it. This data model is based on the [XPath 1.0] data model and earlier work on an [XML Query Data Model]. This document is the result of joint work by the [XSL Working Group] and the [XML Query Working Group].
Editors
Anders Berglund, Mary Fernandez, Ashok Malhotra, Jonathan Marsh, Marton Nagy, Norman Walsh.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines constructor functions, operators and functions on the datatypes defined in [XML Schema Part 2: Datatypes Second Edition] and the datatypes defined in [XQuery 1.0 and XPath 2.0 Data Model]. It also discusses functions and operators on nodes and node sequences as defined in the [XQuery 1.0 and XPath 2.0 Data Model]. These functions and operators are defined for use in [XML Path Language (XPath) 2.0], [XQuery 1.0: An XML Query Language] and [XSL Transformations (XSLT) Version 2.0] and other related XML standards. The signatures and summaries of functions defined in this document are available at: http://www.w3.org/2005/xpath-functions.
Editors
Ashok Malhotra, Jim Melton, Norman Walsh, Michael Kay.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document defines serialization of an instance of the data model as defined in [XQuery 1.0 and XPath 2.0 Data Model] into a sequence of octets. Serialization is designed to be a component that can be used by other specifications such as [XSL Transformations (XSLT) Version 2.0] or [XQuery 1.0: An XML Query Language].
Editors
Scott Boag, Michael Kay, Joanne Tong, Norman Walsh, Henry Zongaro.
XML Query Working GroupXSLT Working Group
- Family:
- Xquery & XSLT
This document specifies usage scenarios for XQuery.
Editors
Don Chamberlin, Peter Fankhauser, Daniela Florescu, Massimo Marchiori, Jonathan Robie.
XML Query Working Group- Family:
- Xquery & XSLT
This document specifies goals, requirements, and usage scenarios for the W3C XML Query (XQuery) data model and query language. It also includes, for each requirement, a corresponding status, indicating the status of the requirement in the XQuery 1.0 family of W3C Recommendations.
Editors
Don Chamberlin, Peter Fankhauser, Massimo Marchiori, Jonathan Robie.
XML Query Working Group- Family:
- Xquery & XSLT
XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.
Editors
James Clark, Steven DeRose.
XML Linking Working Group- Family:
- Xquery & XSLT
This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents.
XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary.
XSLT is also designed to be used independently of XSL. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL.
Editors
James Clark.
XSLT Working Group- Family:
- Xquery & XSLT
Available in:
TürkçeIn progress
This document is a characterization of requirements and use cases for [XSL Transformations (XSLT) Version 2.1]. The Requirements list enhancements requested over time that may be addressed in XSLT 2.1.
Editors
Petr Cimprich.
XSLT Working Group- Family:
- Xquery & XSLT
Internationalization Best Practices for Spec Developers
In progress
This document provides a checklist of internationalization-related considerations when developing a specification. Most checklist items point to detailed supporting information in other documents. Where such information does not yet exist, it can be given a temporary home in this document. The dynamic page Internationalization Techniques: Developing specifications is automatically generated from this document.
Editors
Marcos Caceres, Addison Phillips.
Internationalization Working Group- Family:
- Internationalization Best Practices for Spec Developers
Web App Manifest
Complete
This document is a registry of supplementary members for the Web App Manifest specification that provide additional metadata to an application manifest. This metadata can be used in a digital storefront or other surfaces where this web application may be marketed or ../distributed, or to enhance an installation dialog when installing a web application.
Editors
Aaron Gustafson.
Web Applications Working Group- Family:
- Web App Manifest
Self-Review Questionnaire: Security and Privacy
Complete
This document contains a set of questions to be used when evaluating the security and privacy implications of web platform technologies.
Editors
Theresa O'Connor, Peter Snyder.
Technical Architecture GroupPrivacy Interest Group
- Family:
- Self-Review Questionnaire: Security and Privacy
CSS Cascading and Inheritance
Complete
This CSS module describes how to collate style rules and assign values to all properties on all elements. By way of cascading and inheritance, values are propagated for all properties on all elements.
Editors
Elika Etemad, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Cascading and Inheritance
In progress
By way of cascading and inheritance, values are propagated for all
properties on all elements. New in level 4 are the 'default' keyword
and
Editors
Elika Etemad, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Cascading and Inheritance
Device Posture
In progress
This document specifies an API that allows web applications to request and be notified of changes of the posture of a foldable device.
Editors
Diego Gonzalez-Zuniga, Kenneth Christiansen.
Devices and Sensors Working Group- Family:
- Device Posture
WebRTC
Complete
This document defines a set of ECMAScript APIs in WebIDL to allow media to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices.
Editors
Cullen Jennings, Henrik Boström, Jan-Ivar Bruaroey.
Web Real-Time Communications Working Group- Family:
- WebRTC
In progress
This API defines a control surface for manipulating the network control bits (DSCP bits) of outgoing WebRTC packets, and the queueing priority of outgoing WebRTC packets under congestion.
Editors
Harald Alvestrand.
Web Real-Time Communications Working Group- Family:
- WebRTC
This document describes a set of use cases motivating the development of WebRTC Next Version (WebRTC-NV), as well as the requirements derived from those use cases.
Editors
Bernard Aboba.
Web Real-Time Communications Working Group- Family:
- WebRTC
This document defines a set of ECMAScript APIs in WebIDL to extend the WebRTC 1.0 API to enable user agents to support scalable video coding (SVC).
Editors
Bernard Aboba, Peter Thatcher.
Web Real-Time Communications Working Group- Family:
- WebRTC
This document defines a set of Javascript APIs that allow access to the statistical information about a PeerConnection.
Editors
Harald Alvestrand, Varun Singh, Henrik Boström.
Web Real-Time Communications Working Group- Family:
- WebRTC
This document defines a set of ECMAScript APIs in WebIDL to allow and application using WebRTC to assert an identity, and to mark media streams as only viewable by another identity. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group.
Editors
Cullen Jennings, Martin Thomson.
Web Real-Time Communications Working Group- Family:
- WebRTC
CSS Box Sizing
In progress
This module of CSS defines keywords for the 'width' and 'height' properties to allow a designer to specify that an element should be as small as possible, as large as possible, or as large as possible up to the limit of its containing block. The 'width' and 'height' properties themselves are defined in the CSS Box Model.
Editors
Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Box Sizing
This module extends the CSS sizing properties with keywords that represent content-based "intrinsic" sizes and context-based "extrinsic" sizes, allowing CSS to more easily describe boxes that fit their content or fit into a particular layout context. This is a delta spec over CSS Sizing Level 3.
Editors
Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Box Sizing
Post-Spectre
In progress
Post-Spectre, we need to adopt some new strategies for safe and secure web development. This document outlines a threat model we can share, and a set of mitigation recommendations.
Editors
Mike West.
Web Application Security Working Group- Family:
- Post-Spectre
CSS Basic User Interface
Complete
This section is informative.
CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. It uses various selectors, properties and values to style basic user interface elements in a document. This specification describes those user interface related selectors, properties and values that are proposed for CSS level 3 to style HTML and XML (including XHTML and XForms). It includes and extends user interface related features from the selectors, properties and values of CSS level 2 revision 1 and Selectors specifications.
Editors
Tantek Çelik, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Basic User Interface
Available in:
日本語In progress
CSS Basic UI Level 4 describes CSS properties and values to style basic user interface elements.
Editors
Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Basic User Interface
Media Capabilities
In progress
This specification intends to provide APIs to allow websites to make an optimal decision when picking media content for the user. The APIs will expose information about the decoding and encoding capabilities for a given format but also output capabilities to find the best match based on the device’s display.
Editors
Mounir Lamouri, Chris Cunningham, Vi Nguyen.
Media Working Group- Family:
- Media Capabilities
Fetch Metadata Request Headers
In progress
This document defines a set of Fetch metadata request headers that aim to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used.
Editors
Mike West.
Web Application Security Working Group- Family:
- Fetch Metadata Request Headers
Indexed Database API
Complete
This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure.
Editors
Ali Alabbas, Joshua Bell.
Web Platform Working Group- Family:
- Indexed Database API
This document defines APIs for a database of records holding simple values and hierarchical objects.
Editors
Nikunj Mehta, Jonas Sicking, Eliot Graff, Andrei Popescu, Jeremy Orlow, Joshua Bell.
(historical) Web Applications Working Group- Family:
- Indexed Database API
In progress
This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure.
Editors
Ali Alabbas, Joshua Bell.
Web Applications Working Group- Family:
- Indexed Database API
CSS Scroll Snap
In progress
This module contains features to control panning and scrolling behavior with “snap positions”.
CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.
Editors
Matt Rakow, Jacob Rossi, Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Scroll Snap
CSS Ruby
In progress
The set of CSS properties proposed in this document can be used in combination with the ruby elements of HTML to produce the stylistic effects needed to display ruby text appropriately relative to base text.
Editors
Elika Etemad, Koji Ishii, Xidorn Quan, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Ruby
TTML
Complete
This document defines the application/xml+ttml media type and provides a registry of identified TTML processor profiles.
Editors
Mike Dolan, Nigel Megitt, Glenn Adams.
Timed Text Working Group- Family:
- TTML
This specification improves on ttml-imsc1.1 by supporting contemporary practices, while retaining compatibility with ttml-imsc1.1 documents. It provides one new feature, which permits external font files to be referenced explicitly. One existing feature has been clarified, and no features have been deprecated in this version.
Editors
Pierre-Anthony Lemieux.
Timed Text Working Group- Family:
- TTML
This document specifies the ../distribution format exchange profile (DFXP) of the timed text authoring format (TT AF) in terms of a vocabulary and semantics thereof.
The timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.
The Distribution Format Exchange Profile is intended to be used for the purpose of transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning functions.
In addition to being used for interchange among legacy distribution content formats, DFXP content may be used directly as a distribution format, for example, providing a standard content format to reference from a <text> or <textstream> media object element in a [SMIL 2.1] document.
Editors
Glenn Adams, Pierre-Anthony Lemieux.
Timed Text Working Group- Family:
- TTML
This document specifies the Second Edition of the Timed Text Markup Language (TTML), Version 2, also known as TTML2 (2e), in terms of a vocabulary and semantics thereof.
The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.
It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy ../distribution content formats presently in use for subtitling and captioning functions.
In addition to being used for interchange among legacy ../distribution content formats, TTML Content may be used directly as a distribution format, for example, providing a standard content format to reference from a <track> element in an [HTML] document, or a <text> or <textstream> media element in a [SMIL 3.0] document.
Editors
Glenn Adams, Cyril Concolato.
Timed Text Working Group- Family:
- TTML
This specification defines two profiles of TTML2: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.
Editors
Pierre-Anthony Lemieux.
Timed Text Working Group- Family:
- TTML
This document captures technical requirements for [ttml-imsc1.1], the next revision of [ttml-imsc1.0.1].
Editors
Pierre-Anthony Lemieux.
Timed Text Working Group- Family:
- TTML
This document specifies two profiles of TTML1: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats.
Editors
Pierre-Anthony Lemieux.
Timed Text Working Group- Family:
- TTML
The Simple Online Delivery profile is focused on streamlined delivery of closed captions on the Internet, supporting core TTML features to deliver content originating legacy formats such as CEA-608 and -708 content, and is targeted primarily for delivery in US markets.
Editors
Glenn Adams, Monica Martin, Sean Hayes.
Timed Text Working Group- Family:
- TTML
This document specifies usage scenarios and requirements for a timed text authoring format. A timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.
Editors
Glenn Adams.
Timed Text Working Group- Family:
- TTML
In progress
This document specifies the Second Edition of the Timed Text Markup Language (TTML), Version 2, also known as TTML2 (2e), in terms of a vocabulary and semantics thereof.
The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.
It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy ../distribution content formats presently in use for subtitling and captioning functions.
In addition to being used for interchange among legacy ../distribution content formats, TTML Content may be used directly as a distribution format, for example, providing a standard content format to reference from a <track> element in an [HTML] document, or a <text> or <textstream> media element in a [SMIL 3.0] document.
Editors
Glenn Adams, Cyril Concolato.
Timed Text Working Group- Family:
- TTML
Audio Output Devices API
In progress
This document defines a set of JavaScript APIs that let a Web application manage how audio is rendered on the user audio output devices.
Editors
Justin Uberti, Guido Urdaneta, youenn fablet.
Web Real-Time Communications Working Group- Family:
- Audio Output Devices API
CSS Multi-column Layout
In progress
This module describes multi-column layout in CSS. It builds on the CSS3 Box model module and adds functionality to flow the content of an element into multiple columns.
Editors
Håkon Wium Lie, Florian Rivoal, Rachel Andrew.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Multi-column Layout
Intersection Observer
In progress
This specification describes an API that can be used to understand the visibility and position of DOM elements ("targets") relative to a containing element or to the top-level viewport ("root"). The position is delivered asynchronously and is useful for understanding the visibility of elements and implementing pre-loading and deferred loading of DOM content.
Editors
Stefan Zager, Emilio Cobos Álvarez, Michael Blain.
Web Applications Working Group- Family:
- Intersection Observer
Clipboard API and events
In progress
This document describes apis for clipboard operations such as copy/cut and paste, or drag and drop in web applications.
Editors
Gary Kacmarcik, Grisha Lyukshin.
Web Applications Working Group- Family:
- Clipboard API and events
HTML
Complete
HTML is the World Wide Web's core markup language. Originally, HTML was primarily designed as a language for semantically describing scientific documents. Its general design, however, has enabled it to be adapted, over the subsequent years, to describe a number of other types of documents and even applications.
HTML Working Group- Family:
- HTML
This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device.
Editors
Anssi Kostiainen, Ilkka Oksanen, Dominique Hazaël-Massieux.
Devices and Sensors Working Group- Family:
- HTML
This document contains proposals for new features to be added to HTML to support bidirectional text in languages such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.
Editors
Aharon Lanin, Richard Ishida.
Internationalization Working Group- Family:
- HTML
This specification defines a longdesc attribute to link extended descriptions with images in HTML5-based content.
Editors
Charles McCathieNevile, Mark Sadecki.
HTML Media Extensions Working Group- Family:
- HTML
HTML microdata [MICRODATA] is an extension to HTML used to embed machine-readable data into HTML documents. Whereas the microdata specification describes a means of markup, the output format is JSON. This specification describes processing rules that may be used to extract RDF [RDF-CONCEPTS] from an HTML document containing microdata.
Editors
Gregg Kellogg.
Semantic Web Interest Group- Family:
- HTML
HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. This document may not provide accurate information as the HTML 5 specification is still actively in development. When in doubt, always check the HTML 5 specification itself. [HTML5]
Editors
Simon Pieters.
HTML Media Extensions Working Group- Family:
- HTML
Describes a method for declaring inert DOM subtrees in HTML and manipulating them to instantiate document fragments with identical contents
Editors
Dimitri Glazkov, Rafael Weinstein, Tony Ross.
(historical) Web Applications Working Group- Family:
- HTML
The ruby markup model currently described in the HTML specification is limited in its support for a number of features, notably jukugo and double-sided ruby, as well as inline ruby. This specification addresses these issues by introducing new elements and changing the ruby processing model. Specific care has been taken to ensure that authoring remains as simple as possible.
Editors
Robin Berjon.
HTML Media Extensions Working Group- Family:
- HTML
This document captures the use cases and requirements for standardizing a solution for responsive images.
Editors
Marcos Caceres, Mathew Marquis, Yoav Weiss, David Newton.
HTML Media Extensions Working Group- Family:
- HTML
This document looks at a number of use cases involving ruby, and examines the pros and cons of a number of alternative approaches for meeting those use cases using the current HTML5 model, the XHTML Ruby Annotation model, and two other models. The aim is to clarify which use cases are supported by the existing markup models (HTML5 or XHTML), and where they are not, provide suggestions about how the markup model could be adapted to support those use cases. Implementers and standards developers can then take this background information and the suggestions in this document to specify and implement a comprehensive markup model for ruby in HTML5.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- HTML
This document describes the HTML markup language and provides details to help producers of HTML content create documents that conform to the language. It is not the normative specification but intended for authors.
Editors
Michael[tm] Smith.
HTML Media Extensions Working Group- Family:
- HTML
This document is a strict subset of the HTML5 specification that omits user-agent (UA) implementation details. It is targeted toward Web authors and others who are not UA implementors and who want a view of the HTML specification that focuses more precisely on details relevant to using the HTML language to create Web documents and Web applications.
Editors
Robin Berjon, Travis Leithead, Silvia Pfeiffer, Erika Doyle Navara, Theresa O'Connor.
HTML Media Extensions Working Group- Family:
- HTML
This specification is an extension to the HTML5 specification. It defines an element to be used for the identification of the main content area of a document. The main element formalises the common practice of identification of the main content section of a document using the id values such as 'content' and 'main'. It also defines an HTML element that embodies the semantics and function of the WAI-ARIA landmark role=main.
Editors
Steve Faulkner.
HTML Media Extensions Working Group- Family:
- HTML
This guide aims to help publishers and consumers of HTML data use it well. With several syntaxes and vocabularies to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.
Editors
Jeni Tennison.
Semantic Web Interest Group- Family:
- HTML
XHTML Media Types recapitulates which media types can and should be used with the different flavors of XHTML, and under what conditions.
Editors
Shane McCarron.
XHTML2 Working Group- Family:
- HTML
Available in:
日本語Offline Web Applications highlights the features in HTML 5 that address the challenge of building Web applications that work while offline.
Editors
Anne van Kesteren, Ian Hickson.
HTML Media Extensions Working Group- Family:
- HTML
This paper introduces the concept of a "Rich Web Application Backplane" -- a set of common building blocks for web applications. We argue that submission, data models, model-view binding and behavior, and web components can provide a common infrastructure for multiple markup formats. Further, we propose a common infrastructure for both declarative and imperative web programming languages. By aligning APIs and their declarative representations, we hope to support both implementation approaches and increase interoperability between them.
Editors
Mark Birbeck, John Boyer, Alfred S. Gilman, Kevin Kelly, Steven Pemberton, Charles Wiecha.
Hypertext Coordination Group (Member)- Family:
- HTML
The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 2 event interfaces [DOM2EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup.
Editors
Shane McCarron, Steven Pemberton, T.V. Raman.
XHTML2 Working Group- Family:
- HTML
This document describes XML Schemas for XHTML 1.0.
Editors
Masayasu Ishikawa.
XHTML2 Working Group- Family:
- HTML
The XHTML+SMIL profile defines a set of XHTML abstract modules that support a subset of the SMIL 2.0 specification.
Editors
Aaron Patterson, Patrick Schmitz.
SYMM Working Group- Family:
- HTML
From the early days of the World Wide Web, Web Agents had been extended to support more types of contents. The recent developments of XML and the possibility to mix mupltiple XML Namespaces in the document reiterated the need to extend implementations and relaying on add-on softwares to accomplish tasks not supported by default in the implementation. In other words, we have several XML languages to represent different parts of Web pages (XHTML, SVG, MathML, XForms, etc.), we now need a well defined mechanism that allow different specialized tools to work together and handled these compound documents.
This W3C Note contains a non-exhaustive list of requirements to work on a Component Extension API. The goal of this API is to extend the ability of a Web application. Note that the Web application can be either on the server side or on a client side, and does not automatically implies interaction with a user or having a Web browser.
Editors
Angel Diaz, Jon Ferraiolo, Philippe Le Hégaret, Chris Lilley, Charles McCathieNevile, Tapas Roy, Ray Whitmer.
Hypertext Coordination Group (Member)- Family:
- HTML
"Ruby" are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This document proposes a set of CSS properties associated with the 'Ruby' elements. They can be used in combination with the Ruby elements of HTML.
Editors
Marcin Sawicki, Michel Suignard, Masayasu Ishikawa, Martin Dürst, Tex Texin.
Cascading Style Sheets (CSS) Working Group- Family:
- HTML
Editors
Tomihisa Kamada, Masayasu Ishikawa, Shinichi Matsui.
UNKNOWN WORKING GROUP- Family:
- HTML
Editors
Dan Connolly, Lauren Wood.
UNKNOWN WORKING GROUP- Family:
- HTML
Editors
Stu Weibel.
UNKNOWN WORKING GROUP- Family:
- HTML
In progress
This document defines a way to include and reuse HTML documents in other HTML documents.
Editors
Dimitri Glazkov, Hajime Morita.
Web Platform Working Group- Family:
- HTML
HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. This document describes the set of guiding principles used by the HTML Working Group for the development of HTML5. The principles offer guidance for the design of HTML in the areas of compatibility, utility and interoperability.
Editors
Anne van Kesteren, Maciej Stachowiak.
HTML Media Extensions Working Group- Family:
- HTML
This practical guide provides you with the knowledge required to effectively use the XML Binding Language 2.0. It introduces both the basic and advanced concepts of XBL and describes its syntax and scenarios that should be considered best-practice. It also describes the purpose of the language elements described in the XBL 2.0 specification.
XBL describes the ability to associate elements in one document with script, event handlers, styles, and more complex content models in another document. You can use XBL to re-order and wrap content so that, for instance, simple HTML or XHTML markup can have complex CSS styles applied without requiring that the markup be polluted with multiple div elements. In addition, if you are a programmer, you can use XBL to implement new DOM interfaces, and, in conjunction with other specifications, it enables arbitrary XML tag sets to be treated as "widgets" (pluggable user interface components).
Editors
Lachlan Hunt, Marcos Caceres.
Web Application Formats Working Group- Family:
- HTML
Selection API
In progress
This specification defines APIs to select objects within a document.
Editors
Ryosuke Niwa.
Web Applications Working Group- Family:
- Selection API
WCAG
Complete
Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity, and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make your Web content more usable to users in general.
Editors
Andrew Kirkpatrick, Joshue O Connor, Alastair Campbell, Michael Cooper.
Accessibility Guidelines Working Group- Family:
- WCAG
Provides detailed information about the intent of each WCAG 2.0 success criterion and describes benefits, examples, failure conditions, and recommended techniques in various technologies.
Editors
Michael Cooper, Andrew Kirkpatrick, Joshue O Connor.
Accessibility Guidelines Working Group- Family:
- WCAG
Documents authoring practices in various technologies that may be used to satisfy the WCAG 2.0 success criteria.
Editors
Michael Cooper, Andrew Kirkpatrick, Joshue O Connor.
Accessibility Guidelines Working Group- Family:
- WCAG
WCAG-EM provides an approach for evaluating how websites - including web applications and websites for mobile devices - conform to WCAG 2.0. It covers different situations, including self-assessment and third-party evaluation.
Editors
Eric Velleman, Shadi Abou-Zahra.
Evaluation and Repair Tools Working GroupAccessibility Guidelines Working Group
- Family:
- WCAG
Describes how the Web Content Accessibility Guidelines (WCAG) 2.0 and its principles, guidelines, success criteria and conformance model can be applied to non-Web Information and Communications Technologies (ICT), including non-web documents and software.
Editors
Michael Cooper, Peter Korn, Andi Snow-Weaver, Gregg Vanderheiden.
Accessibility Guidelines Working Group- Family:
- WCAG
Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.
WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material.
WCAG 2.0 succeeds Web Content Accessibility Guidelines 1.0 [WCAG10], which was published as a W3C Recommendation May 1999. Although it is possible to conform either to WCAG 1.0 or to WCAG 2.0 (or both), the W3C recommends that new and updated content use WCAG 2.0. The W3C also recommends that Web accessibility policies reference WCAG 2.0.
Editors
Ben Caldwell, Michael Cooper, Loretta Guarino Reid, Gregg Vanderheiden.
Accessibility Guidelines Working Group- Family:
- WCAG
Requirements used for development of WCAG 2.0.
Editors
Gregg Vanderheiden, John Slatin, Wendy Chisholm.
Accessibility Guidelines Working Group- Family:
- WCAG
This document describes techniques for authoring accessible Hypertext Markup Language (HTML) content (refer to HTML 4.01 [HTML4]). This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author HTML that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.
This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].
Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only.
Editors
Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.
Accessibility Guidelines Working Group- Family:
- WCAG
Gateway to a series of related documents that provide techniques for satisfying the requirements defined in WCAG 1.0.
Editors
Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.
Accessibility Guidelines Working Group- Family:
- WCAG
Techniques that apply across technologies for authors of Web content who wish to claim conformance to WCAG 1.0
Editors
Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.
Accessibility Guidelines Working Group- Family:
- WCAG
This document describes techniques for authoring accessible Cascading Style Sheets (CSS). Cascading Style Sheets are defined by the W3C Recommendations "CSS Level 1" [CSS1] and "CSS Level 2" [CSS2]. This document is intended to help authors of Web content who wish to claim conformance to "Web Content Accessibility Guidelines 1.0" ([WCAG10]). While the techniques in this document should help people author CSS that conforms to "Web Content Accessibility Guidelines 1.0", these techniques are neither guarantees of conformance nor the only way an author might produce conforming content.
This document is part of a series of documents about techniques for authoring accessible Web content. For information about the other documents in the series, please refer to "Techniques for Web Content Accessibility Guidelines 1.0" [WCAG10-TECHS].
Note: This document contains a number of examples that illustrate accessible solutions in CSS but also deprecated examples that illustrate what content developers should not do. The deprecated examples are highlighted and readers should approach them with caution -- they are meant for illustrative purposes only.
Editors
Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.
Accessibility Guidelines Working Group- Family:
- WCAG
Available in:
Brazilian PortugueseThese guidelines explain how to make Web content accessible to people with disabilities. The guidelines are intended for all Web content developers (page authors and site designers) and for developers of authoring tools. The primary goal of these guidelines is to promote accessibility. However, following them will also make Web content more available to all users, whatever user agent they are using (e.g., desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.). Following these guidelines will also help people find information on the Web more quickly. These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.
This is a reference document for accessibility principles and design ideas. Some of the strategies discussed in this document address certain Web internationalization and mobile access concerns. However, this document focuses on accessibility and does not fully address the related concerns of other W3C Activities. Please consult the W3C Mobile Access Activity home page and the W3C Internationalization Activity home page for more information.
This document is meant to be stable and therefore does not provide specific information about browser support for different technologies as that information changes rapidly. Instead, the Web Accessibility Initiative (WAI) Web site provides such information (refer to [WAI-UA-SUPPORT]).
This document includes an appendix that organizes all of the checkpoints by topic and priority. The checkpoints in the appendix link to their definitions in the current document. The topics identified in the appendix include images, multimedia, tables, frames, forms, and scripts. The appendix is available as either a tabular summary of checkpoints or as a simple list of checkpoints.
A separate document, entitled "Techniques for Web Content Accessibility Guidelines 1.0" ([TECHNIQUES]), explains how to implement the checkpoints defined in the current document. The Techniques Document discusses each checkpoint in more detail and provides examples using the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), Synchronized Multimedia Integration Language (SMIL), and the Mathematical Markup Language (MathML). The Techniques Document also includes techniques for document validation and testing, and an index of HTML elements and attributes (and which techniques use them). The Techniques Document has been designed to track changes in technology and is expected to be updated more frequently than the current document. Note. Not all browsers or multimedia tools may support the features described in the guidelines. In particular, new features of HTML 4.0 or CSS 1 or CSS 2 may not be supported.
"Web Content Accessibility Guidelines 1.0" is part of a series of accessibility guidelines published by the Web Accessibility Initiative. The series also includes User Agent Accessibility Guidelines ([WAI-USERAGENT]) and Authoring Tool Accessibility Guidelines ([WAI-AUTOOLS]).
Editors
Wendy Chisholm, Gregg Vanderheiden, Ian Jacobs.
Accessibility Guidelines Working Group- Family:
- WCAG
In progress
The W3C Accessibility Guidelines (WCAG) 3.0 provide a wide range of recommendations for making web content more accessible to users with disabilities. Following these guidelines will address many of the needs of users with blindness, low vision and other vision impairments; deafness and hearing loss; limited movement and dexterity; speech disabilities; sensory disorders; cognitive and learning disabilities; and combinations of these. These guidelines address accessibility of web content on desktops, laptops, tablets, mobile devices, wearable devices, and other web of things devices. They address various types of web content including static content, interactive content, visual and auditory media, and virtual and augmented reality. The guidelines also address related web tools such as user agents (browsers and assistive technologies), content management systems, authoring tools, and testing tools.
Editors
Jeanne F Spellman, Rachael Bradley Montgomery, Shawn Lauriat, Michael Cooper.
Accessibility Guidelines Working Group- Family:
- WCAG
The Requirements for WCAG 3.0 document is the next phase in the development of the next major upgrade to accessibility guidelines that will be the successor to Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance.
Editors
Jeanne F Spellman, Shawn Lauriat, Michael Cooper.
Accessibility Guidelines Working Group- Family:
- WCAG
Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general.
Editors
Charles Adams, Alastair Campbell, Rachael Bradley Montgomery, Michael Cooper, Andrew Kirkpatrick.
Accessibility Guidelines Working Group- Family:
- WCAG
Explores how testability and page-based conformance verification of accessibility guidelines presents challenges for a broad range of websites and web applications.
Editors
Michael Cooper, Peter Korn, Charles Hall.
Accessibility Guidelines Working Group- Family:
- WCAG
This document is a gap analysis and roadmap for the state of accessibility for people with learning and cognitive disabilities when using the Web and information technologies.
Editors
Lisa Seeman-Horwitz, Michael Cooper.
Accessibility Guidelines Working GroupAccessible Platform Architectures Working Group
- Family:
- WCAG
Outlines the requirements that the Web Content Accessibility Guidelines Working Group has set for the development of Web Content Accessibility Guidelines (WCAG) 2.0 extensions. These extension requirements build on the existing requirements for WCAG 2.0, and are designed to work in harmony with the WCAG 2.0 standard.
Editors
Michael Cooper, Andrew Kirkpatrick, Joshue O Connor.
Accessibility Guidelines Working Group- Family:
- WCAG
Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile” describes how the Web Content Accessibility Guidelines (WCAG) 2.0 and its principles, guidelines, and success criteria can be applied to mobile web content, mobile web apps, native apps, and hybrid apps using web components inside native apps. It provides informative guidance, but does not set requirements. It also highlights the relevance of the User Agent Accessibility Guidelines 2.0 in the mobile context.
Editors
Kimberly Patch, Jeanne F Spellman, Kathleen Wahlbin.
Accessibility Guidelines Working GroupUser Agent Accessibility Guidelines Working Group
- Family:
- WCAG
This document provides a review and analysis of guidelines and articles relating to the needs of older people with Web accessibility needs due to ageing, and compares these with the needs of people with disabilities as already addressed in WAI guidelines. The focus is particularly on Europe but applies internationally as well. This review is being undertaken in order to inform the development of educational materials which can better promote the needs of people who have accessibility needs due to ageing, and potential development of profiles and/or extensions on WAI guidelines.
Editors
Andrew Arch.
Accessibility Education and Outreach Working Group (EOWG)- Family:
- WCAG
Web Share API
In progress
This specification defines an API for sharing text, links and other content to an arbitrary destination of the user's choice.
Editors
Matt Giuca, Eric Willigers.
Web Applications Working Group- Family:
- Web Share API
Spatial Data
Complete
This note highlights some of the unique characteristics of spatial data within the broader realm of ethical use of data. A brief analysis of the relationship between law and ethics explains that responsible use is not mandatory. Nevertheless, both legal and ethical frameworks play an important role in shaping what can be considered “responsible”. As do the perspectives of those who interact closely with spatial data: the developers, the users and the regulators. Therefore this note not only provides an insight into the relevant legislation and ethics guidelines, but also considers the principles of ethical data sharing from each of these three perspectives. The principles are made practical by providing concrete communication guidelines and showing examples of good practice.
Editors
JOSEPH ABHAYARATNA, Ed Parsons.
Spatial Data on the Web Interest Group- Family:
- Spatial Data
CSS Pseudo-Elements
In progress
This CSS module defines pseudo-elements, abstract elements that represent portions of the CSS render tree that can be selected and styled.
Editors
Daniel Glazman, Elika Etemad, Alan Stearns.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Pseudo-Elements
CSS Backgrounds and Borders
In progress
This draft contains the features of CSS relating to borders and backgrounds. The main extensions compared to level 2 are borders consisting of images, boxes with multiple backgrounds, boxes with rounded corners and boxes with shadows.
Editors
Bert Bos, Elika Etemad, Brad Kemper.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Backgrounds and Borders
CSS Box Model
In progress
This specification describes the margin and padding properties, which create spacing in and around a CSS box.
Editors
Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Box Model
This specification describes the margin and padding properties, which create spacing in and around a CSS box. It may later be extended to include borders (currently described in [css-backgrounds-3]).
Editors
Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Box Model
CSS
Complete
This document collects together into one definition all the specs that together form the current state of Cascading Style Sheets (CSS) as of 2020. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.
Editors
Tab Atkins Jr., Elika Etemad, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS
CSS Containment
Complete
This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
Editors
Tab Atkins Jr., Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Containment
In progress
This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
Editors
Tab Atkins Jr., Florian Rivoal, Vladimir Levin.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Containment
CSS Grid Layout
In progress
This CSS module defines a two-dimensional grid-based layout system, optimized for user interface design. In the grid layout model, the children of a grid container can be positioned into arbitrary slots in a predefined flexible or fixed-size layout grid. Level 2 expands Grid by adding “subgrid” capabilities for nested grids to participate in the sizing of their parent grids; and aspect-ratio–controlled gutters.
Editors
Tab Atkins Jr., Elika Etemad, Rossen Atanassov.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Grid Layout
The Grid Layout module of CSS allows designers to define invisible grids of horizontal and vertical lines. Elements from a document can then be anchored to points in the grid, which allows them to be visually aligned to each other, even if they are not next to each other in the source.
Editors
Tab Atkins Jr., Elika Etemad, Rossen Atanassov, Oriol Brufau.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Grid Layout
CSS Display
In progress
The CSS Display Module contains the features of CSS relating to the 'display' property and some other box-generation details.
Editors
Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Display
CSS Images
In progress
The draft defines how to refer to images and other external objects from within CSS, including fallback images in different formats, special URLs for vector images of color gradients, and different ways to set the size of images and other objects.
Editors
Tab Atkins Jr., Elika Etemad, Lea Verou.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Images
CSS Custom Highlight API
In progress
This CSS module describes a mechanism for styling arbitrary ranges of a document identified by script.
Editors
Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Custom Highlight API
CSS Conditional Rules
In progress
This module contains the features of CSS for conditional processing of parts of style sheets, conditioned on capabilities of the processor or the document the style sheet is being applied to. It includes and extends the functionality of CSS level 2, which builds on CSS level 1. The main extensions compared to level 2 are allowing nesting of certain at-rules inside @media, and the addition of the @supports rule for conditional processing.
CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.
Editors
David Baron, Elika Etemad, Chris Lilley.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Conditional Rules
This module contains the features of CSS for conditional processing of parts of style sheets. The main extensions compared to level 2 are allowing nesting of certain at-rules inside @media, and the addition of the @supports rule for conditional processing.
Editors
David Baron.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Conditional Rules
Accessibility User Requirements
Complete
Aggregates requirements of a user with disabilities with respect to audio and video on the Web, providing background on user needs, alternative content technologies, and their application on the Web.
Editors
Shane McCarron, Michael Cooper, Mark Sadecki.
Protocols and Formats Working Group- Family:
- Accessibility User Requirements
In progress
Lists user needs and requirements for people with disabilities when using real-time communications (RTC).
Editors
Joshue O Connor, Janina Sajka, Jason White, Michael Cooper.
Accessible Platform Architectures Working Group- Family:
- Accessibility User Requirements
Lists user needs and requirements for people with disabilities when using virtual reality or immersive environments, augmented or mixed reality and other related technologies (XR).
Editors
Joshue O Connor, Janina Sajka, Jason White, Michael Cooper.
Accessible Platform Architectures Working Group- Family:
- Accessibility User Requirements
Describes what people with low vision need for electronic content, tools, and technologies to be accessible. Includes an overview of low vision and describes specific user needs.
Editors
Jim Allan, Andrew Kirkpatrick, Shawn Lawton Henry (TAdER).
Accessibility Guidelines Working Group- Family:
- Accessibility User Requirements
Describes the challenges of using web technologies for users with learning disabilities or cognitive disabilities.
Editors
Lisa Seeman-Horwitz, Michael Cooper.
Protocols and Formats Working GroupAccessibility Guidelines Working Group
- Family:
- Accessibility User Requirements
WebXR
In progress
This specification describes support for various layer types used in a WebXR session.
Editors
Rik Cabanier.
Immersive Web Working Group- Family:
- WebXR
The WebXR Hand Input module expands the [WebXR Device API] with the functionality to track articulated hand poses.
Editors
Manish Goregaokar.
Immersive Web Working Group- Family:
- WebXR
This specification describes support for accessing virtual reality (VR) and augmented reality (AR) devices, including sensors and head-mounted displays, on the Web.
Editors
Brandon Jones, Manish Goregaokar, Nell Waliczek.
Immersive Web Working Group- Family:
- WebXR
The WebXR Augmented Reality module expands the WebXR Device API with the functionality available on AR hardware.
Editors
Brandon Jones, Nell Waliczek, Manish Goregaokar.
Immersive Web Working Group- Family:
- WebXR
This specification module describes support for accessing button, trigger, thumbstick, and touchpad data associated with virtual reality (VR) and augmented reality (AR) devices on the Web.
Editors
Brandon Jones, Nell Waliczek.
Immersive Web Working Group- Family:
- WebXR
Payment Request API
In progress
This specification describes a web API to allow merchants (i.e. web sites selling physical or digital goods) to easily accept payments from different payment methods with minimal integration. User agents (e.g. browsers) will facilitate the payment flow between merchant and user.
Editors
Marcos Caceres, Danyao Wang, Rouslan Solomakhin, Ian Jacobs.
Web Payments Working Group- Family:
- Payment Request API
Web of Things
Complete
This document describes the abstract architecture for the W3C Web of Things. It is derived from a set of use cases and can be mapped onto a variety of concrete deployment scenarios, several examples of which are given.
Editors
Zoltan Kis, Daniel Peintner, Cristiano Aguzzi, Johannes Hund, Kazuaki Nimura.
Web of Things Working Group- Family:
- Web of Things
This document describes a formal model and common representation for a Web of Things (WoT) Thing Description. A Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical entity that provides interactions to and participates in the Web of Things.
Editors
Sebastian Käbisch, Takuki Kamiya, Michael McCool, Victor Charpenay, Matthias Kovatsch.
Web of Things Working Group- Family:
- Web of Things
Available in:
日本語This document describes the abstract architecture for the W3C Web of Things. It is derived from a set of use cases and can be mapped onto a variety of concrete deployment scenarios, several examples of which are given.
Editors
Matthias Kovatsch, Ryuichi Matsukura, Michael Lagally, Toru Kawaguchi, Kunihiko Toumura, Kazuo Kajimoto.
Web of Things Working Group- Family:
- Web of Things
This document describes the initial set of design pattern and vocabulary extensions to the WoT Thing Description that make up the Protocol Binding Templates. It is expected over time that additional protocols will be accommodated by further extending the Binding Templates, adding new vocabulary and new design patterns.
Editors
Michael Koster, Ege Korkan.
Web of Things Working Group- Family:
- Web of Things
This document provides non-normative guidance on Web of Things (WoT) security and privacy. The Web of Things is descriptive, not prescriptive, and so is generally designed to support the security models and mechanisms of the systems it describes, not introduce new ones. However, a WoT system also has its own unique assets, such as a Scripting API and Thing Descriptions, that need to be protected and also have security and privacy implications.
Editors
Elena Reshetova, Michael McCool.
Web of Things Working Group- Family:
- Web of Things
In progress
The WoT Profile specification defines a Profiling Mechanism and a WoT Core Profile, which enables out of the box interoperability among things and devices.
Editors
Michael Lagally, Michael McCool, Ryuichi Matsukura, Sebastian Käbisch, Tomoaki Mizushima.
Web of Things Working Group- Family:
- Web of Things
The WoT Thing Description describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical or virtual entity that provides interactions to and participates in the Web of Things. This specification describes a superset of the features defined in the WoT Thing Description 1.0 specification.
Editors
Sebastian Käbisch, Takuki Kamiya, Michael McCool, Victor Charpenay.
Web of Things Working Group- Family:
- Web of Things
The WoT Architecture specification describes the abstract architecture for the W3C Web of Things based on a set of requirements derived from use cases for multiple application domains. This specification describes a superset of the features defined in the WoT Architecture 1.0 specification.
Editors
Michael Lagally, Ryuichi Matsukura, Toru Kawaguchi, Kunihiko Toumura, Kazuo Kajimoto.
Web of Things Working Group- Family:
- Web of Things
The WoT Discovery specification describes how to discover and obtain the Thing Description of a Thing in a ../distributed environment for various use cases.
Editors
Andrea Cimmino, Michael McCool, Farshid Tavakolizadeh, Kunihiko Toumura.
Web of Things Working Group- Family:
- Web of Things
CSS Lists and Counters
In progress
This CSS level 3 module describes how lists are styled.
Editors
Elika Etemad, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Lists and Counters
CSS Fonts
Complete
This CSS3 module describes how font properties are specified and how font resources are loaded dynamically. The contents of this specification are a consolidation of content previously divided into CSS3 Fonts and CSS3 Web Fonts modules.
Editors
John Daggett, Myles Maxfield, Chris Lilley.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Fonts
Available in:
日本語In progress
This specification adds CSS control of Variable fonts and Chromatic fonts to the features in CSS 3 Fonts, plus other improvements.
Editors
John Daggett, Myles Maxfield, Chris Lilley.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Fonts
CSS Color
Complete
CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. It uses color related properties and respective values to color the text, backgrounds, borders, and other parts of elements in a document. This specification describes color values and properties for foreground color and group opacity. These include properties and values from CSS level 2 and new values.
Editors
Tantek Çelik, Chris Lilley, David Baron.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Color
In progress
This specification describes CSS <color> values and properties for foreground color and group opacity.
Editors
Tab Atkins Jr., Chris Lilley.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Color
This module extends CSS Color 4 to add color modification functions.
Editors
Chris Lilley, Una Kravets, Lea Verou, Adam Argyle.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Color
CSS Values and Units
In progress
CSS Values and Units 4 describes the common values and units that CSS properties accept, and the syntax used for describing them in CSS property definitions.
Editors
Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Values and Units
This CSS3 module describes the various values and units that CSS properties accept. Also, it describes how values are computed from "specified" (which is what the cascading process yields) through "computed" and "used" into "actual" values. The main purpose of this module is to define common values and units in one specification which can be referred to by other modules. As such, it does not make sense to claim conformance with this module alone.
Editors
Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Values and Units
CSS Scroll Anchoring
In progress
Changes in DOM elements above the visible region of a scrolling box can result in the page moving while the user is in the middle of consuming the content.
This spec proposes a mechanism to mitigate this jarring user experience by keeping track of the position of an anchor node and adjusting the scroll offset accordingly.
This spec also proposes an API for web developers to opt-out of this behavior.
Editors
Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Scroll Anchoring
Web Publications
Complete
This specification defines a general manifest format for expressing information about a digital publication. It uses schema.org metadata augmented to include various structural properties about publications, serialized in JSON-LD, to enable interoperability between publishing formats while accommodating variances in the information that needs to be expressed.
Editors
Matt Garrish, Ivan Herman.
Audiobooks Working Group- Family:
- Web Publications
Available in:
日本語This document introduces Portable Web Publications, a vision for the future of digital publishing that is based on a fully native representation of documents within the Open Web Platform. Portable Web Publications achieve full convergence between online and offline/portable document publishing: publishers and users won't need to choose one or the other, but can switch between them dynamically, at will.
Editors
Markus Gylling, Ben De Meester, Ivan Herman, Tzviya Siegman, Dave Cramer, Leonard Rosenthol.
Digital Publishing Interest Group- Family:
- Web Publications
This document describes the set of use cases generated for Annotation and Social Reading within the W3C Digital Publishing Interest Group, in coordination with the Open Annotation Community Group.
Editors
Robert Sanderson.
Digital Publishing Interest Group- Family:
- Web Publications
Web Architecture
Complete
This document contains a set of design principles to be used when designing Web Platform technologies. These principles have been collected during the Technical Architecture Group’s discussions in reviewing developing specifications. We encourage specification designers to read this document and use it as a resource when making design decisions.
Editors
Sangwhan Moon.
Technical Architecture Group- Family:
- Web Architecture
Exposure of settings and characteristics of browsers can impact user privacy by allowing for browser fingerprinting. This document defines different types of fingerprinting, considers ../distinct levels of mitigation for the related privacy risks and provides guidance for Web specification authors on how to balance these concerns when designing new Web features.
Editors
Nick Doty.
Privacy Interest Group- Family:
- Web Architecture
This document is intended to inform future social and legal discussions of the Web by clarifying the ways in which the Web's technical facilities operate to store, publish and retrieve information, and by providing definitions for terminology as used within the Web's technical community. This document also describes the technical and operational impact that does or could result from legal constraints on publishing, linking and transformation on the Web.
Editors
Ashok Malhotra, Larry Masinter, Jeni Tennison, Daniel Appelquist.
Technical Architecture Group- Family:
- Web Architecture
Editors
Robin Berjon, Jungkee Song.
Devices and Sensors Working Group- Family:
- Web Architecture
The Resource Description Framework RDF allows users to describe both Web documents and concepts from the real world—people, organisations, topics, things—in a computer-processable way. Publishing such descriptions on the Web creates the Semantic Web. URIs (Uniform Resource Identifiers) are very important, providing both the core of the framework itself and the link between RDF and the Web. This document presents guidelines for their effective use. It discusses two strategies, called 303 URIs and hash URIs. It gives pointers to several Web sites that use these solutions, and briefly discusses why several other proposals have problems.
Editors
Leo Sauermann, Richard Cyganiak.
Technical Architecture GroupSemantic Web Deployment Working Group
- Family:
- Web Architecture
The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support.
Editors
Ian Jacobs, Norman Walsh.
Technical Architecture Group- Family:
- Web Architecture
This paper addresses and attempts to clarify two issues pertaining to URIs, and presents recommendations. Section 1 addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs. Section 2 describes how URI schemes and URN namespace ids are registered. Section 3 mentions additional unresolved issues not considered by this paper and section 4 presents recommendations.
URI Coordination Group- Family:
- Web Architecture
Available in:
françaisEditors
Johan Hjelm, Henrik Frystyk Nielsen.
UNKNOWN WORKING GROUP- Family:
- Web Architecture
In progress
Capability URLs grant access to a resource to anyone who has the URL. There are times when this is useful, for example one-shot password reset URLs, but overuse can be problematic as URLs cannot generally be kept secret. This document provides some good practices for web developers who wish to incorporate capability URLs into their applications.
Editors
Jeni Tennison.
Technical Architecture Group- Family:
- Web Architecture
This document addresses the issue of the mode in which a URL identifies information about the content or a description of the content by describing how to define data formats and publish the information.
Editors
Jeni Tennison.
Technical Architecture Group- Family:
- Web Architecture
This document recommends best practices for the authors of media type definitions, for the authors of structured syntax suffix definitions (such as +xml), for the authors of specifications that define syntax for fragment identifiers, and for authors that publish documents that are intended to be used with fragment identifiers or who refer to URIs using fragment identifiers.
Editors
Jeni Tennison.
Technical Architecture Group- Family:
- Web Architecture
This document is a guide to versioning XML languages using new XML Schema 1.1 mechanisms. It shows many of the new Schema 1.1 mechanisms, provides context above the schema 1.1 WD, and solicits reader input.
Editors
David Orchard.
XML Schema Working Group- Family:
- Web Architecture
A finding of the W3C Technical Architecture Group (TAG), this document addresses the question of whether or not adding new names to a (published) namespace is a sound practice.
Editors
Norman Walsh.
Technical Architecture Group- Family:
- Web Architecture
Audiobooks
Complete
This specification provides a draft version of an Audiobook Profile for a Web Publication. It also references a framework for packaging audiobooks.
Editors
Wendy Reid, Matt Garrish.
Audiobooks Working Group- Family:
- Audiobooks
CSS Color Adjustment
In progress
This module introduces a model and controls over automatic color adjustment by the user agent to handle user preferences, such as "Dark Mode", contrast adjustment, or specific desired color schemes.
Editors
Elika Etemad, Rossen Atanassov, Rune Lillesveen, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Color Adjustment
Presentation API
In progress
An API to enable web content to access external presentation-type displays and use them for presenting web content.
Editors
Mark Foltz, Dominik Röttsches.
Second Screen Working Group- Family:
- Presentation API
DOM
Complete
DOM defines a platform-neutral model for events, aborting activities, and node trees.
HTML Working Group- Family:
- DOM
Editors
Arnaud Le Hors, Philippe Le Hégaret, Lauren Wood, Gavin Nicol, Jonathan Robie, Mike Champion, Steven B Byrne.
DOM Working Group- Family:
- DOM
Available in:
español
Editors
Johnny Stenback, Andy Heninger.
DOM Working Group- Family:
- DOM
Editors
Ben Chang, Joseph Kesselman, rezaur rahman.
DOM Working Group- Family:
- DOM
In progress
This specification defines various APIs for programmatic access to HTML and generic XML parsers by web applications for use in parsing and serializing DOM nodes.
Editors
Travis Leithead.
Web Platform Working Group- Family:
- DOM
Text Layout Requirements
Complete
Describes requirements for general Japanese layout realized with technologies like CSS, SVG and XSL-FO. The document is mainly based on a standard for Japanese layout, JIS X 4051, however, it also addresses areas which are not covered by JIS X 4051.
Editors
Hiroyuki Chiba, Junzaburo Edamoto, Richard Ishida, Seiichi Kato, Tatsuo KOBAYASHI, Toshi Kobayashi, Nathaniel McCully, Felix Sasaki, Atsushi Shimono, Hajime Shiozawa, Fuqiao Xue.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for general Korean language/Hangul text layout and typography realized with technologies like CSS, SVG and XSL-FO. The document is mainly based on a project to develop the international standard for Korean text layout. It is similar in intent to the Japanese Layout Requirements WG Note.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Text Layout Requirements
In progress
This document summarizes the text composition requirements in the Chinese writing system. One of the goals of the task force is to describe the issues in the Chinese layout requirements, another one is to provide satisfactory equivalent to the current standards (i.e. Unicode), also to promote vendors to implement those relevant features correctly.
Editors
Bobby Tung, Yijun Chen, Eric Q LIU, Hui Jing Chen, Fuqiao Xue, Richard Ishida, An Qi Li, Hai Liang, Xiaoqian Wu, Aijie Zhang.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for the layout and presentation of text in languages that use the Mongolian script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for the layout and presentation of text in the Tibetan script for use with Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode. In addition to Tibet and China, the script is widely used in Bhutan, Nepal, India and throughout the Tibetan diaspora, and requirements for these regions are also included in the scope of the document.
Editors
Richard Ishida, Chunming Hu.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for the layout and presentation of text in languages that use the Tamil script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Text Layout Requirements
A simple set of rules for placement of Ruby text in Japanese typography.
Editors
Florian Rivoal, Atsushi Shimono, Richard Ishida.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes the basic requirements for Indic script layout and text support on the Web and in eBooks. These requirements provide information for Web technologies such as CSS, HTML and SVG about how to support users of Indic scripts. The current document focuses on Devanagari, but there are plans to widen the scope to encompass additional Indian scripts as time goes on.
Editors
Swaran Lata.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for the layout and presentation of text in languages that use the Ethiopic script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.
Editors
Daniel Mekonnen, Richard Ishida.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for the layout and presentation of text in languages that use the Arabic script when they are used by Web standards and technologies, such as HTML, CSS, Mobile Web, Digital Publications, and Unicode.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Text Layout Requirements
This document describes requirements for pagination and layout of books in latin languages, based on the tradition of print book design and composition. It is hoped that these principles can inform the pagination of digital content as well, and serve as a reference for the CSS Working Group and other interested parties. This work was inspired by [JLREQ].
Editors
Dave Cramer.
Digital Publishing Interest Group- Family:
- Text Layout Requirements
Personalization semantics
In progress
This is a requirements document for Personalization Semantics, this document contains use cases, requirements and user stories for personalization semantics.
Editors
Lisa Seeman-Horwitz, Charles LaPierre, Michael Cooper, Ruoxi Ran.
Accessible Platform Architectures Working Group- Family:
- Personalization semantics
Defines standard semantics to enable user driven personalization such as the association of a user-preferred symbols to elements having those semantics.
Editors
Lisa Seeman-Horwitz, Charles LaPierre, Michael Cooper, Ruoxi Ran, Richard Schwerdtfeger.
Accessible Platform Architectures Working Group- Family:
- Personalization semantics
This document provides a vocabulary of terms that can be used to enhance web content with information about controls, symbols, and user interface elements. User agents use these semantics to augment or adapt content to the user scenario. This helps the user use and understand the content, and supports simplification and management of ../distractions.
Editors
Lisa Seeman-Horwitz, Charles LaPierre, Michael Cooper, Ruoxi Ran, Richard Schwerdtfeger.
Accessible Platform Architectures Working Group- Family:
- Personalization semantics
This document lists examples of the personalized help and support properties. This is an extension of Personalization Explainer 1.0. including the properties of literal, numberfree, easylang, alternative, explain, feedback, moreinfo,extrahelp, helptype. It was developed by the Personalization Task Force to provide a vocabulary of terms that can be used to enhance help and support function for web.
Editors
Lisa Seeman-Horwitz, Charles LaPierre, Michael Cooper, Ruoxi Ran, Richard Schwerdtfeger.
Accessible Platform Architectures Working Group- Family:
- Personalization semantics
This document list examples of the tools defined values, this is an extension of Personalization Explainer 1.0. It was developed by the Personalization Task Force to provide a vocabulary of terms that can be used to enhance web tools.
Editors
Lisa Seeman-Horwitz, Charles LaPierre, Michael Cooper, Ruoxi Ran, Richard Schwerdtfeger.
Accessible Platform Architectures Working Group- Family:
- Personalization semantics
../distributed Tracing
Complete
../distributed tracing is a set of tools and practices to monitor the health and reliability of a distributed application. A distributed application is an application that consists of multiple components that are deployed and operated separately. It is also known as micro-service.
Editors
Sergey Kanzhelev, Morgan McLean, Alois Reitbauer, Bogdan Drutu, Nik Molnar, Yuri Shkuro.
Distributed Tracing Working Group- Family:
- ../distributed Tracing
This document provides a registry of identified formats of trace context serialization and deserialization for protocols.
Editors
Sergey Kanzhelev, Philippe Le Hégaret.
Distributed Tracing Working Group- Family:
- ../distributed Tracing
In progress
../distributed tracing is a set of tools and practices to monitor the health and reliability of a distributed application. A distributed application is an application that consists of multiple components that are deployed and operated separately. It is also known as micro-service.
Editors
Sergey Kanzhelev, Morgan McLean, Alois Reitbauer.
Distributed Tracing Working Group- Family:
- ../distributed Tracing
The Screen Orientation API
In progress
Defines APIs to read screen orientation state and to lock the screen orientation to a specific state.
Editors
Mounir Lamouri, Marcos Caceres, Johanna Herman.
Web Applications Working Group- Family:
- The Screen Orientation API
WOFF
Complete
The success of WebFonts is unevenly ../distributed. This study evaluates solutions which would allow WebFonts to be used where slow networks, very large fonts, or complex subsetting requirements currently preclude their use.
Editors
Chris Lilley.
Web Fonts Working Group- Family:
- WOFF
Web Open Font Format (WOFF) 2.0 is a proposed update to the existing WOFF 1.0 with improved compression, even on mobile devices. This is achieved by combining a content-aware preprocessing step and improved entropy coding, compared to the Flate compression used in WOFF 1.0.
Editors
Vladimir Levantovsky, Raph Levien.
Web Fonts Working Group- Family:
- WOFF
Web Open Font Format (WOFF) 2.0 is a proposed update to the existing WOFF 1.0 with improved compression. This report lists requirements for successful deployment, evaluates how the requirement may be met, and examines the compression gains and tradeoffs vs. code complexity, encode and decode time.
Editors
Chris Lilley.
Web Fonts Working Group- Family:
- WOFF
WOFF provides lightweight, easy-to-implement compression of font data for use with CSS @font-face.
Editors
Jonathan Kew, Tal Leming, Erik van Blokland.
Web Fonts Working Group- Family:
- WOFF
CSS Properties and Values API
In progress
This CSS module defines an API for registering new CSS properties. Properties registered using this API are provided with a parse syntax that defines a type, inheritance behaviour, and an initial value.
Editors
Tab Atkins Jr., Daniel Glazman, Alan Stearns, Greg Whitworth, Shane Stephens.
Cascading Style Sheets (CSS) Working GroupTechnical Architecture Group
- Family:
- CSS Properties and Values API
Language Tags and Locale Identifiers for the World Wide Web
In progress
Describes mechanisms based on BCP 47 for identifying or selecting the language of content or locale preferences used to process information using Web technologies.
Editors
Addison Phillips.
Internationalization Working Group- Family:
- Language Tags and Locale Identifiers for the World Wide Web
Resource Hints
In progress
Resource Hints provides hints that authors may use to assist the user agent in fetching resources to improve page performance.
Editors
Ilya Grigorik.
Web Performance Working Group- Family:
- Resource Hints
Screen Wake Lock API
In progress
This document specifies an API that allows web applications to request a screen wake lock. Under the right conditions, and if allowed, the screen wake lock prevents the system from turning off a device's screen.
Editors
Kenneth Christiansen, Marcos Caceres, Raphael Kubo da Costa.
Devices and Sensors Working Group- Family:
- Screen Wake Lock API
Worklets
In progress
This specification defines an API for running scripts in stages of the rendering pipeline independent of the main javascript execution environment.
Editors
Ian Kilpatrick.
Cascading Style Sheets (CSS) Working GroupTechnical Architecture Group
- Family:
- Worklets
CSS Inline Layout
In progress
This module describes the positioning in the block progression direction both of elements and text within lines and of the lines themselves. It also describes special features for formatting of first lines and drop caps.
Editors
Dave Cramer, Elika Etemad, Steve Zilles.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Inline Layout
WebDriver
Complete
This specification defines the WebDriver API, a platform-and language-neutral interface that allows programs or scripts to introspect into, and control the behaviour of, a web browser.
Editors
Simon Stewart, David Burns.
Browser Testing and Tools Working Group- Family:
- WebDriver
In progress
This specification defines the WebDriver API, a platform-and language-neutral interface that allows programs or scripts to introspect into, and control the behaviour of, a web browser.
Editors
Simon Stewart, David Burns.
Browser Testing and Tools Working Group- Family:
- WebDriver
Media Queries
Complete
HTML4 and CSS2 currently support media-dependent style sheets tailored for different media types. For example, a document may use sans-serif fonts when displayed on a screen and serif fonts when printed. ‘screen’ and ‘print’ are two media types that have been defined. Media queries extend the functionality of media types by allowing more precise labeling of style sheets.
A media query consists of a media type and zero or more expressions to limit the scope of style sheets. Among the media features that can be used in media queries are ‘width’, ‘height’, and ‘color’. By using media queries, presentations can be tailored to a specific range of output devices without changing the content itself.
Editors
Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- Media Queries
In progress
Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered. They are used in the CSS @media rule to conditionally apply styles to a document, and in various other contexts and languages, such as HTML and JavaScript.
Editors
Dean Jackson, Florian Rivoal, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- Media Queries
Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered.
Editors
Florian Rivoal, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- Media Queries
Permissions
In progress
The Permissions API allows a web application to be aware of the status of a given permission, to know whether it is granted, denied or if the user will be asked whether the permission should be granted.
Editors
Mounir Lamouri, Marcos Caceres, Jeffrey Yasskin.
Web Application Security Working Group- Family:
- Permissions
Permissions Policy
In progress
This specification defines a mechanism that allows developers to selectively enable and disable use of various browser features and APIs.
Editors
Ian Clelland.
Web Application Security Working Group- Family:
- Permissions Policy
JSON-LD
Complete
JSON is a useful data serialization and messaging format. This specification defines JSON-LD, a JSON-based format to serialize Linked Data. The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. It is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines.
Editors
Gregg Kellogg, Pierre-Antoine Champin, Dave Longley.
JSON-LD Working Group- Family:
- JSON-LD
Available in:
日本語This specification defines a set of algorithms for programmatic transformations of JSON-LD documents. Restructuring data according to the defined transformations often dramatically simplifies its usage. Furthermore, this document proposes an Application Programming Interface (API) for developers implementing the specified algorithms.
Editors
Gregg Kellogg, Dave Longley, Pierre-Antoine Champin.
JSON-LD Working Group- Family:
- JSON-LD
JSON-LD Framing allows developers to query by example and force a specific tree layout to a JSON-LD document.
Editors
Dave Longley, Gregg Kellogg, Pierre-Antoine Champin.
JSON-LD Working Group- Family:
- JSON-LD
JSON-LD offers a JSON-based serialization for Linked Data. One of the primary uses of JSON-LD is its ability to exchange RDF data across the Web. This can be done by first serializing RDF to JSON-LD, after which data consumers can deserialize JSON-LD to RDF.
Editors
Ruben Taelman.
JSON-LD Working Group- Family:
- JSON-LD
Time Ontology
Complete
OWL-Time is an ontology for temporal entities, with a particular focus on the description of relations between time intervals. However, there are certain relations between more general temporal entities (in particular, time instants) that cannot be expressed using the 15 interval relations defined in OWL-Time. This note adds four new relations: time:equals, time:hasInside, time:disjoint and time:notDisjoint which complement the original relations and allow for description of more relationships between temporal entities.
Editors
Simon Cox, Chris Little.
Spatial Data on the Web Interest Group- Family:
- Time Ontology
OWL-Time is an ontology for temporal entities and relations between them. OWL-Time defines simple temporal entities (intervals and instants). This note adds one new class time:TemporalAggregate and two properties time:hasPart and its inverse time:isPartof to allow for the description of arbitrary aggregates of temporal entities.
Editors
Simon Cox, Adam Shepherd, Charles Vardeman.
Spatial Data on the Web Interest Group- Family:
- Time Ontology
In progress
The OWL-Time ontology is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological relations among instants and intervals, together with information about durations, and about temporal position including date-time information.
Editors
Simon Cox, Chris Little.
Spatial Data on the Web Working Group- Family:
- Time Ontology
Media Timed Events
Complete
This document collects use cases and requirements for improved support for timed events related to audio or video media on the web, where synchronization to a playing audio or video media stream is needed, and makes recommendations for new or changed web APIs to realize these requirements. The goal is to extend the existing support in HTML for text track cue events to add support for dynamic content replacement cues and generic metadata events that drive synchronized interactive media experiences, and improve the timing accuracy of rendering of web content intended to be synchronized with audio or video media playback.
Editors
Chris Needham.
Media and Entertainment Interest Group- Family:
- Media Timed Events
CSS Overflow
In progress
CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This module contains the features of CSS relating to new mechanisms of overflow handling in visual media (e.g., screen or paper). In interactive media, it describes features that allow the overflow from a fixed size container to be handled by pagination (displaying one page at a time). It also describes features, applying to all visual media, that allow the contents of an element to be spread across multiple fragments, allowing the contents to flow across multiple regions or to have different styles for different fragments.
Editors
David Baron, Elika Etemad, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Overflow
CSS Overflow allows the contents of an element to be spread across multiple fragments, allowing the contents to flow across multiple regions or to have different styles for different fragments.
Editors
David Baron, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Overflow
CSS Positioned Layout
In progress
CSS Positioned Layout defines the five ways to lay out elements with CSS: four ways from CSS level 2 ('static', 'relative', 'absolute' and 'fixed') and a fifth way, to position elements relative to a page box.
Editors
Elika Etemad, Tab Atkins Jr., Rossen Atanassov, Arron Eicholz.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Positioned Layout
CSS Text Decoration
In progress
This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.
Editors
Elika Etemad, Koji Ishii.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Text Decoration
This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.
Editors
Elika Etemad, Koji Ishii.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Text Decoration
CSS Box Alignment
In progress
This module contains the features of CSS relating to the alignment of boxes within their containers in the various CSS box layout models: block layout, table layout, flex layout, and grid layout.
Editors
Elika Etemad, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Box Alignment
Lightweight Packaging Format (LPF)
Complete
This specification defines a file format and processing model for packaging into a single-file container the set of related resources and associated metadata that comprise a digital publication.
Editors
Laurent Le Meur.
Audiobooks Working Group- Family:
- Lightweight Packaging Format (LPF)
Available in:
繁體中文Pronunciation
In progress
The objective of the Pronunciation Task Force is to develop normative specifications and best practices guidance collaborating with other W3C groups as appropriate, to provide for proper pronunciation in HTML content when using text to speech (TTS) synthesis. This document presents the results of the Pronunciation Task Force work on an HTML standard. It includes an introduction with a historical perspective, an enumeration of the core requirements, a listing of approach use cases, and finally a gap analysis. Gaps are defined when a requirement does not have a corresponding use case approach by which it can be authored in HTML.
Editors
Markku Hakkinen, Steve Noble, Dee Dyer, Irfan Ali, Paul Grenier, Ruoxi Ran.
Accessible Platform Architectures Working Group- Family:
- Pronunciation
The objective of the Pronunciation Task Force is to develop normative specifications and best practices guidance collaborating with other W3C groups as appropriate, to provide for proper pronunciation in HTML content when using text to speech (TTS) synthesis. This document defines a standard mechanism to allow content authors to include spoken presentation guidance in HTML content. Also, it contains two identified approaches and enumerates their advantages and disadvantages.
Editors
Markku Hakkinen, Irfan Ali.
Accessible Platform Architectures Working Group- Family:
- Pronunciation
The objective of the Pronunciation Task Force is to develop normative specifications and best practices guidance collaborating with other W3C groups as appropriate, to provide for proper pronunciation in HTML content when using text to speech (TTS) synthesis. This document provides various user scenarios highlighting the need for standardization of pronunciation markup, to ensure that consistent and accurate representation of the content. The requirements that come from the user scenarios provide the basis for the technical requirements/specifications.
Editors
Irfan Ali, Sam Kanta, Christine Loew, Paul Grenier, Ruoxi Ran.
Accessible Platform Architectures Working Group- Family:
- Pronunciation
CSS Speech
In progress
CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. CSS defines aural properties that give control over rendering XML to speech. This draft describes the text to speech properties proposed for CSS level 3. These are designed for match the model described in the Speech Synthesis Markup Language (SSML) Version 1.0 [SSML10]
The CSS3 Speech Module is a community effort and if you would like to help with implementation and driving the specification forward along the W3C Recommendation track, please contact the editors.
Editors
Daniel Weck.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Speech
CSS Transforms
In progress
CSS Transforms 2 adds new transform functions and properties for three-dimensional transforms, and convenience functions for simple transforms.
Editors
Tab Atkins Jr., Simon Fraser, Dean Jackson, Theresa O'Connor.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Transforms
CSS transforms allows elements styled with CSS to be transformed in two-dimensional or three-dimensional space.
Editors
Simon Fraser, Dean Jackson, Theresa O'Connor, Dirk Schulze.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Transforms
Resize Observer
In progress
This specification describes an API for observing changes to Element’s size.
Editors
Aleks Totic, Greg Whitworth.
Cascading Style Sheets (CSS) Working Group- Family:
- Resize Observer
Push API
In progress
An API that provides Web applications with scripted access to server-sent application data.
Editors
Peter Beverloo, Martin Thomson.
Web Applications Working Group- Family:
- Push API
Semantic Sensor Network
Complete
The Semantic Sensor Network Ontology (commonly known as "SSN" is an ontology for describing sensors and the observations they make of the physical world. SSN is published in a modular architecture that supports the judicious use of "just enough" ontology for diverse applications, including satellite imagery, large scale scientific monitoring, industrial and household infrastructure, citizen observers, and Web of Things.
Editors
Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois.
Spatial Data on the Web Working Group- Family:
- Semantic Sensor Network
In progress
The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. This note describes some extensions to the SSN ontology to enable:
- linking to the ultimate feature-of-interest for an observation, act of sampling, or actuation, alongside the link to the (proximate) feature-of-interest, which might be a sample
- homogeneous collections of observations, in which one or more of the feature-of-interest, ultimate feature-of-interest, observed-property, procedure, sensor, phenomenon-time or result-time may be shared by all members of the collection
Editors
Simon Cox.
Spatial Data on the Web Interest Group- Family:
- Semantic Sensor Network
Dataset exchange
Complete
The Profiles Ontology is an RDF vocabulary to describe profiles of (one or more) standards for information resources. It describes the general pattern of narrowing the scope of a specification with additional, but consistent, constraints, and is particularly relevant to data exchange situations where conformance to such profiles is expected and carries additional context. The Profiles Ontology enables profile descriptions to specify the role of resources related to data exchange such as schemas, ontologies, rules about use of controlled vocabularies, validation tools, and guidelines. The ontology may however be used to describe the role of artifacts in any situation where constraints are made on a the usage of more general specifications.
Editors
Nicholas Car.
Dataset Exchange Working Group- Family:
- Dataset exchange
This document lists use cases iteratively compiled by the Dataset Exchange Working Group. They identify current shortcomings and motivate the extension of the Data Catalog Vocabulary (DCAT). Further, they motivate the creation of guidelines for and a formalisation of the concept of (application) profiles and how to describe those, and the need for a mechanism to exchange information about those profiles including profile-based content-negotiation.
Editors
Jaroslav Pullmann, Rob Atkinson, Antoine Isaac, Ixchel Faniel.
Dataset Exchange Working Group- Family:
- Dataset exchange
ADMS is a profile of DCAT, used to describe semantic assets (or just 'Assets'), defined as highly reusable metadata (e.g. xml schemata, generic data models) and reference data (e.g. code lists, taxonomies, dictionaries, vocabularies) that are used for eGovernment system development.
Editors
Phil Archer, Gofran Shukair.
Government Linked Data Working Group- Family:
- Dataset exchange
Editors
Keith Alexander, Richard Cyganiak, Michael Hausenblas, Jun Zhao.
Semantic Web Interest Group- Family:
- Dataset exchange
In progress
This document describes how Internet clients may negotiate for content provided by servers according toprofiles. This is ../distinct from negotiating by Media Type or Language: the profile is expected to specify the content of information returned, which may be a subset of the information the responding server has about the requested resource, and may be structured in a specific way to meet interoperability requirements of a community of practice.
Editors
Lars G. Svensson, Nicholas Car.
Dataset Exchange Working Group- Family:
- Dataset exchange
Sensor API
Complete
The Motion Sensors Explainer Note is an introduction to low-level and high-level motion sensors, their relationship, inner workings and common use-cases.
Editors
Kenneth Christiansen, Alexander Shalamov.
Devices and Sensors Working Group- Family:
- Sensor API
In progress
This specification defines accelerometer sensor interface for obtaining information about acceleration applied to the X, Y and Z axis of a device that hosts the sensor.
Editors
Anssi Kostiainen.
Devices and Sensors Working Group- Family:
- Sensor API
The Orientation Sensor API extends the Generic Sensor API to provide generic information describing the device’s physical orientation in relation to a three dimensional Cartesian coordinate system.
Editors
Kenneth Christiansen, Anssi Kostiainen.
Devices and Sensors Working Group- Family:
- Sensor API
This specification defines a concrete sensor interface to monitor the rate of rotation around the device’s local three primary axes.
Editors
Anssi Kostiainen.
Devices and Sensors Working Group- Family:
- Sensor API
The Generic Sensor API defines a framework and abstract Sensor interface to provide a consistent basis for writing for concrete sensor specifications. It is intended to be extended to accommodate different sensor types.
Editors
Rick Waldron.
Devices and Sensors Working Group- Family:
- Sensor API
This specification defines a concrete sensor interface to measure magnetic field in the X, Y and Z axis.
Editors
Anssi Kostiainen, Rijubrata Bhaumik.
Devices and Sensors Working Group- Family:
- Sensor API
This specification defines a means to receive events that correspond to a light sensor detecting the presence of a light.
Editors
Anssi Kostiainen.
Devices and Sensors Working Group- Family:
- Sensor API
This specification defines a means to receive events that correspond to a proximity sensor detecting the presence of a physical object.
Editors
Anssi Kostiainen, Rijubrata Bhaumik.
Devices and Sensors Working Group- Family:
- Sensor API
This specification defines the GeolocationSensor interface for obtaining geolocation of the hosting device.
Editors
Anssi Kostiainen, Thomas Steiner.
Devices and Sensors Working Group- Family:
- Sensor API
CSS Writing Modes
Complete
This module specifies the text layout model in CSS and the properties that control it. It covers bidirectional and vertical text.
Editors
Elika Etemad, Koji Ishii.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Writing Modes
Available in:
日本語In progress
CSS Writing Modes Level 4 defines CSS support for various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts).
Editors
Elika Etemad, Koji Ishii.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Writing Modes
Inaccessibility of CAPTCHA
Complete
Various approaches have been employed over many years to ../distinguish human users of web sites from robots. While the traditional CAPTCHA approach of asking the user to identify obscured text in an image remains common, other mechanisms are gaining in prominence. These approaches generally require users to perform a task believed to be possible for humans and difficult for robots, but the nature of the task inherently excludes many people with disabilities, resulting in an incorrect denial of service to these users. Research findings also indicate that many popular CAPTCHA techniques are no longer particularly effective or secure, so it is necessary to consider alternative approaches to block robots, yet ensure these approaches support access for people with disabilities. This document examines a number of potential solutions that allow systems to test for human users, and the extent to which these solutions adequately accommodate people with disabilities.
Editors
Scott Hollier, Janina Sajka, Jason White, Michael Cooper, Matthew May.
Accessible Platform Architectures Working Group- Family:
- Inaccessibility of CAPTCHA
WebAssembly
Complete
This document provides an explicit JavaScript API for interacting with WebAssembly.
Editors
Daniel Ehrenberg.
WebAssembly Working Group- Family:
- WebAssembly
This document describes the integration of WebAssembly with the broader web platform.
Editors
Daniel Ehrenberg.
WebAssembly Working Group- Family:
- WebAssembly
This document describes version 1.0 of the core WebAssembly standard, a safe, portable, low-level code format designed for efficient execution and compact representation.
Editors
Andreas Rossberg.
WebAssembly Working Group- Family:
- WebAssembly
CSS Spatial Navigation
In progress
This specification defines a general model for navigating the focus using the arrow keys, as well as related CSS, JavaScript features and Events.
Editors
Jihye Hong, Florian Rivoal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Spatial Navigation
Service Workers
In progress
This specification enables applications to take advantage of persistent background processing, including hooks to enable bootstrapping of Web applications while offline.
Editors
Alex Russell, Jungkee Song, Jake Archibald, Marijn Kruisselbrink.
Service Workers Working Group- Family:
- Service Workers
Verifiable Credentials
Complete
Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable.
Editors
Manu Sporny, Grant Noble, Dave Longley, Daniel Burnett, Brent Zundel.
Verifiable Credentials Working Group- Family:
- Verifiable Credentials
Available in:
한국어This document provides implementation guidance for Verifiable Credentials.
Editors
Andrei Sambra.
Verifiable Credentials Working Group- Family:
- Verifiable Credentials
A verifiable claim is a qualification, achievement, quality, or piece of information about an entity's background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness. The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.
Editors
Shane McCarron, Joe Andrieu, Matt Stone, Tzviya Siegman, Gregg Kellogg, Ted Thibodeau.
Verifiable Credentials Working Group- Family:
- Verifiable Credentials
Accessibility Conformance Testing
Complete
This is a W3C Recommendation. Defines a format for writing accessibility test rules for automated testing tools and manual testing methodologies. It can be used for evaluation to different accessibility standards, such as the W3C Web Content Accessibility Guidelines (WCAG).
Editors
Wilco Fiers, Maureen Kraft, Mary Jo Mueller, Shadi Abou-Zahra.
Accessibility Guidelines Working Group- Family:
- Accessibility Conformance Testing
This document is a companion to the Accessibility Conformance Testing (ACT) Rules Format 1.0 specification. It lists common input aspects as defined by the ACT Rules Format 1.0 specification. This document is informative. It provides a reference to well defined input aspects to assist authors in writing ACT Rules and to support the consistency of ACT Rules.
Editors
Wilco Fiers, Maureen Kraft, Mary Jo Mueller, Shadi Abou-Zahra.
Accessibility Guidelines Working Group- Family:
- Accessibility Conformance Testing
MiniApp
In progress
This document introduces a new format for mobile application, named MiniApp, which is a very popular hybrid solution relies on Web technologies but also integrates with capabilities of Native Apps.
Editors
Angel Li, Qing An, Dapeng Liu, Hongru (Judy) Zhu, Qingqian Tao, Zhixing Lei, Zhou Shen, Zhiqiang Yu, Wanming Lin, xiaowei jiang, Fuqiao Xue, Lei Zhao.
Chinese Web Interest Group- Family:
- MiniApp
Pointer Lock
Complete
API that provides scripted access to raw mouse movement data while locking the target of mouse events to a single element and removing the cursor from view.
Editors
Vincent Scheib.
Web Platform Working Group- Family:
- Pointer Lock
In progress
This specification defines an API that provides scripted access to raw mouse movement data while locking the target of mouse events to a single element and removing the cursor from view. This is an essential input mode for certain classes of applications, especially first person perspective 3D applications and 3D modeling software.
Editors
Navid Zolghadr.
Web Applications Working Group- Family:
- Pointer Lock
CSS Generated Content
In progress
This CSS3 Module describes how to insert content in a document.
Editors
Elika Etemad, Dave Cramer.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Generated Content
CSS Table
In progress
This CSS module defines a two-dimensional grid-based layout system, optimized for tabular data rendering. In the table layout model, each display node is assigned to an intersection between a set of consecutive rows and a set of consecutive columns, themselves generated from the table structure and sized according to their content.
Editors
François Remy, Greg Whitworth, David Baron.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Table
CSS Syntax
In progress
This CSS3 module describes the basic structure of CSS style sheets, some of the details of the syntax, and the rules for parsing CSS style sheets. It also describes (in some cases, informatively) how stylesheets can be linked to documents and how those links can be media-dependent. Additional details of the syntax of some parts of CSS described in other modules will be described in those modules. The selectors module has a grammar for selectors. Modules that define properties give the grammar for the values of those properties, in a format described in this document.
Editors
Tab Atkins Jr., Simon Sapin.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Syntax
Preload
In progress
This specification defines the preload relationship of the HTML Link Element (<link>).
Editors
Ilya Grigorik, Yoav Weiss.
Web Performance Working Group- Family:
- Preload
CSS Animation Worklet API
In progress
The Animation Worklet API provides a method to create scripted animations that control a set of animation effects. The API is designed to make it possible for user agents to run such animations in their own dedicated thread to provide a degree of performance isolation from main thread.
Editors
Majid Valipour, Robert Flack, Stephen McGruer.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Animation Worklet API
Strings on the Web: Language and Direction Metadata
In progress
This document describes the best practices for identifying language and base direction for strings used on the Web. The concepts in this document are applicable any time strings are used on the Web, either as part of a formalised data structure, but also where they simply originate from JavaScript scripting or any stored list of strings.
Editors
Addison Phillips, Richard Ishida.
Internationalization Working Group- Family:
- Strings on the Web: Language and Direction Metadata
CSS Overscroll Behavior
In progress
This module defines overscroll-behavior to control the behavior when the scroll position of a scroll container reaches the edge of the scrollport. This allows content authors to hint that the boundary default actions, such as scroll chaining and overscroll, should not be triggered.
Editors
Majid Valipour.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Overscroll Behavior
Input Events
In progress
This specification defines additions to events for text and related input to allow for the monitoring and manipulation of default browser behavior in the context of text editor applications and other applications that deal with text input and text formatting. This specification builds on the UI events spec.
Editors
Johannes Wilm, Ben Peters.
Web Applications Working Group- Family:
- Input Events
This specification defines additions to events for text and related input to allow for the monitoring and manipulation of default browser behavior in the context of text editor applications and other applications that deal with text input and text formatting. This specification builds on the UI events spec.
Editors
Johannes Wilm.
Web Applications Working Group- Family:
- Input Events
UI Events
In progress
This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2 [DOM2 Events].
Editors
Gary Kacmarcik, Travis Leithead, Doug Schepers.
Web Applications Working Group- Family:
- UI Events
This specification defines the values for the KeyboardEvent.code attribute which is defined in DOM 3 Events.
Editors
Gary Kacmarcik, Travis Leithead.
Web Platform Working Group- Family:
- UI Events
This specification defines the values for the KeyboardEvent.key attribute which is defined in DOM 3 Events.
Editors
Gary Kacmarcik, Travis Leithead.
Web Platform Working Group- Family:
- UI Events
DeviceOrientation Event
In progress
This specification defines several new DOM event types that provide information about the physical orientation and motion of a hosting device.
Editors
Rich Tibbett, Tim Volodine, Stephen Block, Andrei Popescu.
Devices and Sensors Working Group- Family:
- DeviceOrientation Event
WebVTT
In progress
This specification defines WebVTT, the Web Video Text Tracks format. Its main use is for marking up external text track resources in connection with the HTML
Editors
Silvia Pfeiffer.
Timed Text Working Group- Family:
- WebVTT
Character Model for the World Wide Web
Complete
Architectural Specification providing authors of specifications, software developers, and content developers with a common reference for normalization and string identity matching to improve interoperable text handling on the World Wide Web.
Editors
Addison Phillips.
Internationalization Working Group- Family:
- Character Model for the World Wide Web
Available in:
日本語This document was written as the first step towards a character model for W3C specifications, to make sure that the requirements of other W3C Working Groups (and of other interested parties) are understood and can be addressed.
Editors
Martin Dürst.
Internationalization Working Group- Family:
- Character Model for the World Wide Web
This Architectural Specification provides authors of specifications, software developers, and content developers with a common reference for interoperable text manipulation on the World Wide Web, building on the Universal Character Set, defined jointly by the Unicode Standard and ISO/IEC 10646. Topics addressed include use of the terms 'character', 'encoding' and 'string', a reference processing model, choice and identification of character encodings, character escaping, and string indexing.
For normalization and string identity matching, see the companion document Character Model for the World Wide Web 1.0: Normalization [CharNorm]. For resource identifiers, see the companion document Character Model for the World Wide Web 1.0: Resource Identifiers [CharIRI].
Editors
Martin Dürst, François Yergeau, Richard Ishida, Misha Wolf, Tex Texin.
Internationalization Working Group- Family:
- Character Model for the World Wide Web
Credential Management
In progress
This specification describes an imperative API enabling a website to request a user’s credentials from a user agent, and to help the user agent correctly store user credentials for future use.
Editors
Mike West.
Web Application Security Working Group- Family:
- Credential Management
CSS Fragmentation
In progress
This module describes the fragmentation model that partitions a flow into pages, columns, or regions. It builds on the Page model module and introduces and defines the fragmentation model. It adds functionality for pagination, breaking variable fragment size and orientation, widows and orphans.
Editors
Rossen Atanassov, Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Fragmentation
This CSS module defines the style properties that specify the points in a document where text may be broken to start a new page, a new column, or any similar kind of region.
Editors
Rossen Atanassov, Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Fragmentation
Filter Effects
In progress
Filter effects are a way of processing an element's rendering before it is displayed in the document. Typically, rendering an element via CSS or SVG can conceptually described as if the element, including its children, are drawn into a buffer (such as a raster image) and then that buffer is composited into the elements parent. Filters apply an effect before the compositing stage. Examples of such effects are blurring, changing color intensity and warping the image.
Although originally designed for use in SVG, filter effects are a set a set of operations to apply on an image buffer and therefore can be applied to nearly any presentational environment, including CSS. They are triggered by a style instruction (the ‘filter’ property). This specification describes filters in a manner that allows them to be used in content styled by CSS, such as HTML and SVG. It also defines a CSS property value function that produces a CSS
Editors
Dirk Schulze, Dean Jackson.
Cascading Style Sheets (CSS) Working Group- Family:
- Filter Effects
Motion Path
In progress
The Motion Path module of CSS defines an additional way to define the position and rotation of elements when rendering a document. The position is given by a trajectory and an offset along that trajectory between 0 and 100%. In combination with animations, the offset can also be animated.
Editors
Dirk Schulze, Shane Stephens, Jihye Hong, Eric Willigers.
Cascading Style Sheets (CSS) Working Group- Family:
- Motion Path
Geometry Interfaces
In progress
This specification provides basic geometric interfaces.
Editors
Simon Pieters, Chris Harrelson.
Cascading Style Sheets (CSS) Working Group- Family:
- Geometry Interfaces
Selectors
Complete
Selectors are patterns that match against elements in a tree. Selectors have been optimized for use with HTML and XML, and are designed to be usable in performance-critical code.
CSS (Cascading Style Sheets) is a language for describing the rendering of HTML and XML documents on screen, on paper, in speech, etc. CSS uses Selectors for binding style properties to elements in the document. This document describes extensions to the selectors defined in CSS level 2. These extended selectors will be used by CSS level 3.
Selectors define the following function:
expression ∗ element → boolean
That is, given an element and a selector, this specification defines whether that element matches the selector.
These expressions can also be used, for instance, to select a set of elements, or a single element from a set of elements, by evaluating the expression across all the elements in a subtree. STTS (Simple Tree Transformation Sheets), a language for transforming XML trees, uses this mechanism. [STTS]
Editors
Tantek Çelik, Elika Etemad, Daniel Glazman, Ian Hickson, Peter Linss, John Williams.
Cascading Style Sheets (CSS) Working Group- Family:
- Selectors
In progress
Selectors are patterns that match against elements in a tree. They are a core component of CSS (Cascading Style Sheets), which uses Selectors to bind style properties to elements in a document.
Editors
Elika Etemad, Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- Selectors
CSS Flexible Box Layout
In progress
The draft describes a CSS box model optimized for interface design. It provides an additional layout system alongside the ones already in CSS. [CSS21] In this new box model, the children of a box are laid out either horizontally or vertically, and unused space can be assigned to a particular child or ../distributed among the children by assignment of “flex” to the children that should expand. Nesting of these boxes (horizontal inside vertical, or vertical inside horizontal) can be used to build layouts in two dimensions.
Editors
Tab Atkins Jr., Elika Etemad, Rossen Atanassov, David Baron.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Flexible Box Layout
CSS Shadow Parts
In progress
CSS Shadow Parts defines the ::part() pseudo-element on shadow hosts, allowing shadow hosts to selectively expose chosen elements from their shadow tree to the outside page for styling purposes.
Editors
Tab Atkins Jr., Fergal Daly.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Shadow Parts
CSS Paged Media
In progress
This module describes the page model that partitions a flow into pages. It builds on the Box model module and introduces and defines the page model and paged media. It adds functionality for pagination, page margins, page size and orientation, headers and footers, widows and orphans, and image orientation. Finally it extends generated content to enable page numbering and running headers / footers.
Editors
Elika Etemad, Simon Sapin.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Paged Media
CSS Animations
In progress
CSS Animations allow an author to modify CSS property values over time.
Editors
Dean Jackson, David Baron, Tab Atkins Jr., Brian Birtles.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Animations
CSS Transitions
In progress
CSS Transitions allows property changes in CSS values to occur smoothly over a specified duration.
Editors
David Baron, Dean Jackson, Brian Birtles, David Hyatt.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Transitions
Web Animations
In progress
This specification defines a model for synchronization and timing of changes to the presentation of a Web page. This specification also defines an application programming interface for interacting with this model and it is expected that further specifications will define declarative means for exposing these features.
Editors
Brian Birtles, Robert Flack, Stephen McGruer, Antoine Quint, Shane Stephens, Alex Danilo, Tab Atkins Jr..
SVG Working GroupCascading Style Sheets (CSS) Working Group
- Family:
- Web Animations
SVG
Complete
This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 1.1, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML.
Editors
Erik Dahlström, Patrick Dengler, Anthony Grasso, Chris Lilley, Cameron McCormack, Doug Schepers, Jonathan Watt, Jon Ferraiolo, Jun Fujisawa, Dean Jackson.
SVG Working Group- Family:
- SVG
Available in:
日本語This specification defines the features and syntax for Scalable Vector Graphics (SVG) Tiny, Version 1.2, a language for describing two-dimensional vector graphics in XML, combined with raster graphics and multimedia. Its goal is to provide the ability to create a whole range of graphical content, from static images to animations to interactive Web applications. SVG 1.2 Tiny is a profile of SVG intended for implementation on a range of devices, from cellphones and PDAs to laptop and desktop computers, and thus includes a subset of the features included in SVG 1.1 Full, along with new features to extend the capabilities of SVG. Further extensions are planned in the form of modules which will be compatible with SVG 1.2 Tiny, and which when combined with this specification, will match and exceed the capabilities of SVG 1.1 Full.
Editors
Ola Andersson, Robin Berjon, Erik Dahlström, Andrew Emmons, Jon Ferraiolo, Anthony Grasso, Vincent Hardy, Scott Hayman, Dean Jackson, Chris Lilley, Cameron McCormack, Andreas Neumann, Craig Northway, Antoine Quint, Nandini Ramani, Doug Schepers, Andrew Shellshear.
SVG Working Group- Family:
- SVG
This document defines two mobile profiles of SVG 1.1. The first profile, SVG Tiny, is defined to be suitable for cellphones; the second profile, SVG Basic, is suitable for PDAs.
Editors
Tolga Capin.
SVG Working Group- Family:
- SVG
Available in:
DeutschIn progress
This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 2, a language for describing two-dimensional vector and mixed vector/raster graphics. Although an XML serialization is given, processing is defined in terms of a DOM.
Editors
Amelia Bellamy-Royds, Bogdan Brinza, Chris Lilley, Dirk Schulze, David Storey, Eric Willigers.
SVG Working Group- Family:
- SVG
This specification defines a syntax and DOM representation for paths, which are shapes that can be rendered in a document. Paths are primarily used for rendering shapes using the SVG 'path' element, but are also used by a number of other Web platform features, such as clipping paths and rendering in an HTML 'canvas'.
Editors
Cyril Concolato, Cameron McCormack, Doug Schepers.
SVG Working Group- Family:
- SVG
This specification defines SVG markers, a feature for placing re-usable graphical elements along the outline of an SVG shape.
Editors
Cameron McCormack.
SVG Working Group- Family:
- SVG
This specification defines properties for controlling the appearance of strokes painted for SVG shapes.
Editors
Cameron McCormack, Dirk Schulze.
SVG Working Group- Family:
- SVG
SVG Integration defines how SVG documents must be processed when used in various contexts, such as CSS background images, HTML ‘iframe’ elements, and so on. These requirements include which features are restricted or disabled, such as scripting and animation.
Editors
Cameron McCormack, Doug Schepers, Dirk Schulze.
SVG Working Group- Family:
- SVG
This specification extends SVG for color-managed environments such as print, photography and graphics arts.
Editors
Chris Lilley, Anthony Grasso.
SVG Working Group- Family:
- SVG
This primer explains SVG for color-managed environments.
Editors
Chris Lilley, Anthony Grasso.
SVG Working Group- Family:
- SVG
This specification extends SVG with a declarative way to incorporate parameter values into reusable SVG content.
Editors
Doug Schepers.
SVG Working Group- Family:
- SVG
This primer explains a declarative way to incorporate parameter values into reusable SVG content.
Editors
Doug Schepers.
SVG Working Group- Family:
- SVG
This specification extends SVG to allow two-dimensional objects to be displayed using three-dimensional transformations, to allow animated effects such as flipping, zooming and perspective.
Editors
Jun Fujisawa, Anthony Grasso.
SVG Working Group- Family:
- SVG
This primer explains how a wide variety of raster filter effects can be applied to content such as SVG and HTML/CSS.
Editors
Erik Dahlström.
SVG Working Group- Family:
- SVG
This specification allows a wide variety of raster filter effects to be applied to content such as SVG and HTML/CSS, by combining a set of filter primitives.
Editors
Erik Dahlström.
SVG Working Group- Family:
- SVG
The requirements for SVG versions after SVG 1.0.
Editors
Dean Jackson.
SVG Working Group- Family:
- SVG
Device Memory
In progress
This document defines a HTTP Client Hint header to surface device capability for memory i.e. device RAM, in order to enable web apps to customize content depending on device memory constraints.
Editors
Shubhie Panicker.
Web Performance Working Group- Family:
- Device Memory
Reporting
In progress
Navigation Error Logging defines an API to store and retrieve error data related to the previous navigations of a document.
Editors
Douglas Creager, Ilya Grigorik, Julia Tuttle, Alois Reitbauer, Arvind Jain, Jatinder Mann.
Web Performance Working Group- Family:
- Reporting
CSS Scrollbars
In progress
CSS Scrollbars standardizes the ability to color scrollbars introduced in 2000 by Windows IE 5.5. This is useful when building web applications which use color schemes very different from the appearance of default platform scrollbars.
Editors
Tantek Çelik, Rossen Atanassov.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Scrollbars
CSS Logical Properties and Values
In progress
CSS Logical Properties and Values Level 1 defines properties that indirectly set certain other CSS properties (including width, margin, float, text-align and page-break) based on the writing mode: left-to-right, right-to-left or top-to-bottom. They are useful in simple, generic style sheets, such as User Agent style sheets, but may also save a few lines in styles for documents with both left-to-right and right-to-left text.
Editors
Rossen Atanassov, Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Logical Properties and Values
CSS Painting API
In progress
This specification describes an API which allows developers to paint a part of an box in response to geometry / computed style changes with an additional <image> function.
Editors
Ian Kilpatrick, Dean Jackson.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Painting API
EXI
Complete
The Efficient XML Interchange (EXI) format is a compact representation that simultaneously optimizes performance and the utilization of computational resources. The EXI format was designed to support XML representation. With a relatively small set of transformations it may also be used for JSON, a popular format for exchange of structured data on the Web.
Editors
Daniel Peintner, Don Brutzman.
Efficient Extensible Interchange Working Group- Family:
- EXI
The specification of the canonical form of EXI 1.0, for use in applications that need document signature without the burden of going through plain-text XML (e.g. in constrained environments)
Editors
Sebastian Käbisch, Daniel Peintner.
Efficient Extensible Interchange Working Group- Family:
- EXI
This profile of the EXI 1.0 specification allows restrictions on the memory consumption of EXI internal structures. It is intended for application areas and devices that are not capable or allowed to require arbitrary memory growth at runtime. Certain evaluations of EXI in the context of such areas exposed some challenges to the attempt to restrict memory usage predictably within their limited respective threshold.
Editors
Youenn Fablet, Daniel Peintner.
Efficient Extensible Interchange Working Group- Family:
- EXI
Efficient XML Interchange (EXI) is a compact XML-specific format that does not require an XML parser on the receiving end; it is stream-based and supports both compression and Schema-aware coding to save even more bandwidth. The second edition clarifies a number of issues raised by implementers.
Editors
John Schneider, Takuki Kamiya, Daniel Peintner, Rumen Kyusakov.
Efficient Extensible Interchange Working Group- Family:
- EXI
This document describes the processes and results of the XML Binary Characterization Working Group in evaluating the need and feasibility of a "binary XML" recommendation. It includes an analysis of which properties such a format must possess. It recommends that the W3C produce a "binary XML" recommendation and enumerates the minimum requirements which this "binary XML" recommendation must meet.
Editors
Oliver Goldman, Dmitry Lenkov.
XML Binary Characterization Working Group- Family:
- EXI
This document describes measurement aspects, methods, caveats, test data, and test scenarios for evaluating the potential benefits of a candidate binary XML format.
Editors
Stephen Williams, Peter Haggar.
XML Binary Characterization Working Group- Family:
- EXI
This document is the result of a study to identify desirable properties in an XML format. An XML format is a format that is capable of representing the information in an XML document. The properties have been derived from requirements induced by use cases collected in the [XBC Use Cases] document. Properties are divided into two categories: algorithmic and format. Besides these two categories, Section 6 Additional Considerations lists additional considerations which, because of the difficulty to establish an accurate measurement, have not been listed as properties but are nonetheless relevant for an accurate comparison between different proposals.
Editors
Michael Cokus, Santiago Pericas-Geertsen.
XML Binary Characterization Working Group- Family:
- EXI
This document describes use cases for evaluating the potential benefits of an efficient serialization format for XML. The use cases are documented here to understand the constraints involved in environments for which XML employment may be problematic because of one or more characteristics of XML. Desirable properties of XML and alternative formats to address the use cases are derived and discussed in a separate publication of the XML Binary Characterization Working Group (XBC WG) [XBC Properties].
Editors
Michael Cokus, Santiago Pericas-Geertsen.
XML Binary Characterization Working Group- Family:
- EXI
In progress
This is a non-normative document intended to provide an easily readable technical background on the Efficient XML Interchange (EXI) format. It is oriented towards quickly understanding how the EXI format can be used in practice and how options can be set to achieve specific needs. Section 2. Concepts describes the structure of an EXI document and introduces the notions of EXI header, EXI body and EXI grammar which are fundamental to the understanding of the EXI format. Additional details about data type representation, compression, and their interaction with other format features are presented. Finally, Section 3. Efficient XML Interchange by Example provides a detailed, bit-level description of a schema-less example.
Editors
Daniel Peintner, Santiago Pericas-Geertsen.
Efficient Extensible Interchange Working Group- Family:
- EXI
This Working Draft is an evaluation of the Efficient XML Interchange (EXI) Format 1.0 with reference to the Properties identified by the XML Binary Characterization (XBC) Working Group, relative to XML, gzipped XML and ASN.1 PER. It is conducted using the XBC Measurement methodology. For the "compactness" and "processing efficiency" Properties, the performance is measured with EXI Measurement framework, over the test data collected for the EXI measurements, representing XBC Use Cases.
Editors
Carine Bournez.
Efficient Extensible Interchange Working Group- Family:
- EXI
The Efficient XML Interchange (EXI) format defines a new representation for the Extensible Markup Language (XML) Information Set. The introduction of such a format may cause disruption in systems that have so far been able to assume XML as the only representation of XML Information Set data. This document reviews areas where the introduction of EXI may disrupt or otherwise have an impact on existing XML technologies, XML processors, and applications. It also describes EXI design features and steps that may be taken by implementors to reduce or eliminate disruption and impacts.
Editors
Jaakko Kangasharju.
Efficient Extensible Interchange Working Group- Family:
- EXI
The purpose of this document is to provide guidelines for the interoperable deployment of the Efficient XML Interchange (EXI) format. It provides explanations of format features and techniques to support interoperable information exchanges using EXI. While intended primarily as a practical guide for systems architects and programmers, it also presents information suitable for the general reader interested in EXI's intended role in the expanding Web.
Editors
Michael Cokus, Daniel Vogelheim.
Efficient Extensible Interchange Working Group- Family:
- EXI
This Working Group Note presents measurement results of various high-performance XML interchange encoding formats and their associated processors, made by the Efficient XML Interchange (EXI) Working Group. The measurements have been conducted following the recommendations of the XML Binary Characterization (XBC) Working Group. In particular, this draft covers measurements of the properties of "compactness", "processing efficiency" and "roundtrip support", as defined by the XBC WG. We start by describing the context in which this analysis is being made, and the position of an efficient format in the landscape of high performance XML strategies. Then we describe the measured quantities in detail and the test framework in which they were made, and give a short description of each format. Finally, a summary of the results and the conclusions of the group are included. The full measurements and analysis are included in an appendix and supporting documents.
As a result of the measurements described here, the working group selected Efficient XML ([EffXML]) to be the basis for the proposed encoding specification to be prepared as a candidate W3C Recommendation. Follow up work has centered around integrating some features from the other measured format technologies, particularly variations for both more efficient structural and value encodings.
Editors
Greg White, Jaakko Kangasharju, Don Brutzman, Stephen Williams.
Efficient Extensible Interchange Working Group- Family:
- EXI
CSS Layout API
In progress
This specification describes an API which allows developers to layout a box in response to computed style and box tree changes.
Editors
Greg Whitworth, Ian Kilpatrick, Tab Atkins Jr., Shane Stephens, Robert O'Callahan, Rossen Atanassov.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Layout API
CSSOM
In progress
Converting CSSOM value strings into meaningfully typed JavaScript representations and back can incur a significant performance overhead. This specification exposes CSS values as typed JavaScript objects to facilitate their performant manipulation.
Editors
Shane Stephens, Tab Atkins Jr., Naina Raisinghani.
Cascading Style Sheets (CSS) Working GroupTechnical Architecture Group
- Family:
- CSSOM
CSSOM defines APIs (including generic parsing and serialization rules) for Media Queries, Selectors, and CSS itself.
Editors
Simon Pieters, Glenn Adams.
Cascading Style Sheets (CSS) Working Group- Family:
- CSSOM
The APIs introduced by this specification provide authors with a way to inspect and manipulate the view information of a document. This includes getting the position of element layout boxes, obtaining the width of the viewport through script, and also scrolling an element.
Editors
Simon Pieters.
Cascading Style Sheets (CSS) Working Group- Family:
- CSSOM
ODRL
Complete
The ODRL permissions and obligations expression language provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing statements about digital content usage. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL statements .
Editors
Renato Iannella, Serena Villata.
Permissions and Obligations Expression Working Group- Family:
- ODRL
Available in:
日本語The ODRL permissions and obligations expression language provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for describing statements about digital content usage. The ODRL Vocabulary and Expression describes the terms used in such statements and how to encode them.
Editors
Renato Iannella, Michael Steidl, Stuart Myles, Víctor Rodríguez-Doncel.
Permissions and Obligations Expression Working Group- Family:
- ODRL
Available in:
日本語Vehicle Information Service Specification
In progress
The W3C Vehicle Signal Server Specification defines a WebSocket based API that enables client applications running on the In-Vehicle-Infotainment system and on the local vehicle network to access vehicle signals and data attributes. The purpose of the specification is to promote a Server API that enables application development in a consistent manner across participating automotive manufacturers.
Editors
Kevin Gavigan, Adam Crofts, Wonsuk Lee, Powell Kinney.
Automotive Working Group- Family:
- Vehicle Information Service Specification
ActivityPub
Complete
The ActivityPub protocol is a social networking protocol based upon the ActivityStreams 2.0 data format. It is based upon experience gained from implementing and working with the OStatus and Pump.io protocols.
Editors
Christopher Webber, Jessica Tallon.
Social Web Working Group- Family:
- ActivityPub
WebSub
Complete
An open, simple, web-scale and decentralized HTTP-based pubsub protocol. Publishers register a hub, and subscribers make a subscription request to their desired publisher's hub. Hubs manage subscription requests and ../distribution of new content to subscribers.
Editors
Julien Genestoux, Aaron Parecki.
Social Web Working Group- Family:
- WebSub
IndieAuth
Complete
IndieAuth is an identity layer on top of OAuth 2.0 [RFC6749], primarily used to obtain an OAuth 2.0 Bearer Token [RFC6750] for use by [Micropub] clients. End-Users and Clients are all represented by URLs. IndieAuth enables Clients to verify the identity of an End-User, as well as to obtain an access token that can be used to access resources under the control of the End-User.
Editors
Aaron Parecki.
Social Web Working Group- Family:
- IndieAuth
Social Web
Complete
Post Type Discovery specifies an algorithm for determining the type of a post by what properties it has and potentially what value(s) they have, which helps avoid the need for explicit post types that are being abandoned by modern post creation UIs.
Editors
Tantek Çelik.
Social Web Working Group- Family:
- Social Web
This document describes a JSON serialization format to describe simple streams of data as well as single objects of data for data transfer and processing.
Editors
Benjamin Roberts.
Social Web Working Group- Family:
- Social Web
The Social Web Protocols are a collection of standards which enable various aspects of decentralised social interaction on the Web. This document describes the purposes of each, and how they fit together.
Editors
Amy Guy.
Social Web Working Group- Family:
- Social Web
CSS Counter Styles
In progress
This module introduces the ‘@counter-style’ rule, which allows authors to define their own custom counter styles for use with CSS list-marker and generated-content counters. It also predefines a set of common counter styles.
Editors
Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Counter Styles
Clear Site Data
In progress
This document defines an imperative mechanism which allows web developers to instruct a user agent to clear a user’s locally stored data related to a host and its subdomains.
Editors
Mike West.
Web Application Security Working Group- Family:
- Clear Site Data
Remote Playback API
In progress
This specification defines an API extending the HTMLMediaElement that enables controlling remote playback of media from a web page onto remote playback devices such as connected TVs, projectors or audio-only speakers, attached using wired (HDMI, DVI, or similar) and wireless technologies (Miracast, Chromecast, DLNA, AirPlay, or similar).
Editors
Mounir Lamouri, Anton Vayvod.
Second Screen Working Group- Family:
- Remote Playback API
Page Visibility
Complete
This specification defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web applications.
Editors
Jatinder Mann, Arvind Jain.
Web Performance Working Group- Family:
- Page Visibility
In progress
Page Visibility defines a means to programmatically determine the visibility state of a document. This can aid in the development of power and CPU efficient web applications.
Editors
Ilya Grigorik, Arvind Jain, Jatinder Mann.
Web Performance Working Group- Family:
- Page Visibility
Cooperative Scheduling of Background Tasks
In progress
The requestIdleCallback method is a more appropriate way for scheduling background tasks during times when the browser would otherwise be idle.
Editors
Ross McIlroy, Ilya Grigorik.
Web Performance Working Group- Family:
- Cooperative Scheduling of Background Tasks
Geospatial data
Complete
This document advises on best practices related to the publication and usage of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application.
Editors
Jeremy Tandy, Linda van den Brink, Payam Barnaghi.
Spatial Data on the Web Working Group- Family:
- Geospatial data
This document shows how dense geospatial raster data can be represented using the W3C RDF Data Cube ontology in concert with other popular ontologies. SPARQL queries can then be served through an OGC Discrete Global Grid System for observations, coupled with a triple store for observational metadata.
Editors
Dmitry Brizhinev, Sam Toyer, Kerry Taylor.
Spatial Data on the Web Working Group- Family:
- Geospatial data
An extension to the RDF Data Cube ontology to support specification of key metadata required to interpret spatio-temporal data. QB4ST provides generalized support for numeric and other ordered references systems, particularly Spatial Reference Systems and Temporal Reference Systems.
Editors
Rob Atkinson.
Spatial Data on the Web Working Group- Family:
- Geospatial data
This Note describes CoverageJSON, a data format for describing "coverage" data in JavaScript Object Notation (JSON), and provides an overview of its design and capabilities. The primary intended purpose of the format is to enable data transfer between servers and web browsers, to support the development of interactive, data-driven web applications.
Editors
Jon Blower, Maik Riechert, Bill Roberts.
Spatial Data on the Web Working Group- Family:
- Geospatial data
This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC.
Editors
Frans Knibbe, Alejandro Llaves.
Spatial Data on the Web Working Group- Family:
- Geospatial data
EME
Complete
This specification extends the HTMLMediaElement interface to provide APIs for controlling playback of protected content
Editors
David Dorwin, Jerry Smith, Mark Watson, Adrian Bateman.
HTML Media Extensions Working Group- Family:
- EME
The document defines the Initialization Data formats for use with the Encrypted Media Extensions API.
HTML Media Extensions Working Group- Family:
- EME
This document defines the stream formats for use with the Encrypted Media Extensions API.
HTML Media Extensions Working Group- Family:
- EME
This document defines the stream format for using ISO Base Media File Format content that uses the ISO Common Encryption ('cenc') protection scheme with the Encrypted Media Extensions API.
HTML Media Extensions Working Group- Family:
- EME
This document defines the "cenc" Initialization Data format for use with the Encrypted Media Extensions API. It is commonly used with the ISO Common Encryption ('cenc') Protection Scheme for ISO Base Media File Format Stream Format.
HTML Media Extensions Working Group- Family:
- EME
This document defines the "keyids" Initialization Data format for use with the Encrypted Media Extensions API. It defines a stream format-independent format for specifying a list of key ID(s).
HTML Media Extensions Working Group- Family:
- EME
PNG
Complete
This specification defines a mechanism for storing images that use the Reference PQ EOTF specified in [BT2100-1] in the Portable Network Graphics (PNG) format, without modification to existing chunks or the introduction of new chunks.
Editors
Pierre-Anthony Lemieux.
Timed Text Working Group- Family:
- PNG
This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits.
PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store gamma and chromaticity data for improved color matching on heterogeneous platforms.
This specification defines an Internet Media Type image/png.
Editors
David Duce.
UNKNOWN WORKING GROUP- Family:
- PNG
Long Tasks API
In progress
This document defines an API that web page authors can use to detect presence of “long tasks” that monopolize the UI thread for extended periods of time and block other critical tasks from being executed - e.g. reacting to user input.
Editors
Shubhie Panicker, Ilya Grigorik, Domenic Denicola.
Web Performance Working Group- Family:
- Long Tasks API
SHACL
Complete
SHACL (Shapes Constraint Language) is a language for describing and constraining the contents of RDF graphs. SHACL groups these descriptions and constraints into "shapes", which specify conditions that apply at a given RDF node. Shapes provide a high-level vocabulary to identify predicates and their associated cardinalities, datatypes and other constraints. Additional constraints can be associated with shapes using SPARQL and similar extension languages. These extension languages can also be used to define new high-level vocabulary terms. SHACL shapes can be used to communicate information about data structures associated with some process or interface, generate or validate data, or drive user interfaces. This document defines the SHACL language and its underlying semantics.
Editors
Holger Knublauch, Dimitris Kontokostas.
RDF Data Shapes Working Group- Family:
- SHACL
To foster the development of Shapes Constraint Language (SHACL) this document includes a set of use cases and requirements that motivate a simple language and semantics for formulating structural constraints on RDF graphs. All use cases provide realistic examples describing how people may use structural constraints to validate RDF instance data.
Editors
Simon Steyskal, Karen Coyle.
RDF Data Shapes Working Group- Family:
- SHACL
This document describes advanced features of the Shapes Constraint Language (SHACL) including features to define custom targets, annotation properties, user-defined functions, node expressions and rules. While many of these features rely on SPARQL, they also define extension points that can be used by other implementation languages.
Editors
Holger Knublauch, Dean Allemang, Simon Steyskal.
RDF Data Shapes Working Group- Family:
- SHACL
This document defines a JavaScript-based extension mechanism for the Shapes Constraint Language (SHACL). It defines a syntax for declaring constraints, constraint components, functions, rules and targets in JavaScript. Using this syntax, SHACL shapes can benefit from the rich expressive power of JavaScript. In order to ensure that the resulting JavaScript code can be executed across platforms, this document defines a (minimalistic) JavaScript API that needs to be implemented by supporting engines.
Editors
Holger Knublauch, Pano Maria.
RDF Data Shapes Working Group- Family:
- SHACL
Cloud Browser Architecture
Complete
A Cloud Browser is a browser running and executing on a server. This document describes the concepts and architecture for the Cloud Browser. The main purpose is to provide the building blocks for a Cloud Browser solution.
Editors
Colin Meerveld, Alexandra Mikityuk.
Media and Entertainment Interest Group- Family:
- Cloud Browser Architecture
Activity Streams
Complete
This specification details a model for representing potential and completed activities using the JSON format.
Editors
James Snell, Evan Prodromou.
Social Web Working Group- Family:
- Activity Streams
This specification describes the Activity vocabulary.
Editors
James Snell, Evan Prodromou.
Social Web Working Group- Family:
- Activity Streams
Micropub
Complete
Micropub is an open API standard that is used to create posts on one's own domain using third-party clients. Web apps and native apps (e.g. iPhone, Android) can use Micropub to post short notes, photos, events or other posts to your own site.
Editors
Aaron Parecki.
Social Web Working Group- Family:
- Micropub
Linked Data Platform
Complete
Linked Data Notifications is a protocol to facilitate exchanging messages between applications which serve as senders, receivers and/or consumers of RDF data.
Editors
Sarven Capadisli, Amy Guy.
Social Web Working Group- Family:
- Linked Data Platform
Available in:
日本語Linked Data Patch Format (LD Patch) defines a language for expressing a sequence of operations to apply to Linked Data resources; it is suitable for use with the HTTP PATCH method.
Editors
Alexandre Bertails, Pierre-Antoine Champin, Andrei Sambra.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
This document describes a HTTP-based protocol for clients and servers to be able to efficiently retrieve large Linked Data Platform Resource representations by splitting up the responses into separate URL-addressable page resources.
Editors
Steve Speicher, John Arwe, Ashok Malhotra.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
This primer provides an introduction to the Linked Data Platform (LDP), with examples illustrating the principal concepts such as the notion of an LDP resource and the LDP container and how they can be used by Web clients.
Editors
Nandana Mihindukulasooriya, Roger Menday.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
A set of best practices and simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF.
Editors
Steve Speicher, John Arwe, Ashok Malhotra.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
Available in:
日本語This note discusses use cases and requirements for Access Control for the Linked Data Platform WG. It also outlines a charter for developing a standard for HTTP-based access control. The work delineated in the charter may be pursued in the Linked Data Platform WG or an independent, related WG.
Editors
Ashok Malhotra.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
This document provides best practices and guidelines for implementing Linked Data Platform servers and clients.
Editors
Cody Burleson, Miguel Esteban Gutiérrez, Nandana Mihindukulasooriya.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
A set of user stories, use cases, scenarios and requirements that motivate a simple read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF.
Editors
Steve Battle, Steve Speicher.
Linked Data Platform (LDP) Working Group- Family:
- Linked Data Platform
CSS Fill and Stroke
In progress
This module contains the features of CSS relating to filling and stroking text and SVG shapes.
Editors
Elika Etemad, Tab Atkins Jr..
SVG Working GroupCascading Style Sheets (CSS) Working Group
- Family:
- CSS Fill and Stroke
CSS Image Values and Replaced Content
In progress
The specification describes how CSS uses images: external images linked via a URL, sets of fallback images and various built-in color gradients. Images can be resized or cropped.
Editors
Tab Atkins Jr., Elika Etemad, Lea Verou.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Image Values and Replaced Content
Beacon
In progress
This specification defines an interoperable means for site developers to asynchronously transfer data from the user agent to a web server, with the user agent taking the responsibility to eventually send the data.
Editors
Ilya Grigorik, Alois Reitbauer, Arvind Jain, Jatinder Mann.
Web Performance Working Group- Family:
- Beacon
CSS Rhythmic Sizing
In progress
This specification allows controlling sizes of CSS objects to be multiple of a unit, for example to produce a consistent vertical typographic rhythm.
Editors
Koji Ishii, Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Rhythmic Sizing
Web Annotations
Complete
The Web Annotation Data Model specfication describes a structured model and format to enable annotations to be shared and reused across different hardware and software platforms to support a wide variety of simple as well as complex application use cases.
Editors
Robert Sanderson, Paolo Ciccarese, Benjamin Young.
Web Annotation Working Group- Family:
- Web Annotations
Available in:
日本語Annotations are typically used to convey information about a resource or associations between resources. Simple examples include a comment or tag on a single web page or image, or a blog post about a news article.
The Web Annotation Protocol describes the transport mechanisms for creating and managing annotations in a method that is consistent with the Web Architecture and REST best practices.
Editors
Robert Sanderson.
Web Annotation Working Group- Family:
- Web Annotations
Available in:
日本語The Web Annotation Vocabulary specifies the set of RDF classes, predicates and named entities that are used by the Web Annotation Data Model. It also lists recommended terms from other ontologies that are used in the model, and provides the JSON-LD Context and profile definitions needed to use the Web Annotation JSON serialization in a Linked Data context.
Editors
Robert Sanderson, Paolo Ciccarese, Benjamin Young.
Web Annotation Working Group- Family:
- Web Annotations
Available in:
日本語This document does not define any new approach to selection. Instead, it relies on existing techniques, providing a common model and syntax to express and possibly combine selections. The formal specification and the semantics originate from a separate Recommendation, namely the Web Annotation Data Model, where it is used to select targets of annotations. The current document only “extracts” Selectors and States from that data model; by doing so, it makes their usage easier for applications developers whose concerns are not related to annotations.
Editors
Ivan Herman, Robert Sanderson, Paolo Ciccarese, Benjamin Young.
Web Annotation Working Group- Family:
- Web Annotations
This Note describes and illustrates potential approaches for including annotations within HTML documents. Examples also are included illustrating the use within an HTML document of annotation Selectors as fragment identifiers.
Editors
Timothy Cole, Sarven Capadisli, Benjamin Young, Ivan Herman.
Web Annotation Working Group- Family:
- Web Annotations
POE
In progress
This document includes a set of use cases and requirements, compiled by the Permissions & Obligations Expression (POE) working group, that motivate the expression of statements about digital content usage. All use cases provide realistic examples describing how people and organisations may (or want to be able to) specify statements about digital content usage. The requirements derived from these use cases will be used to guide the development of the POE WG recommendation deliverables for the Information Model, Vocabulary and Encodings.
Editors
Michael Steidl, Simon Steyskal, Benedict Whittam Smith.
Permissions and Obligations Expression Working Group- Family:
- POE
Internationalization for HTML
Complete
This document describes numbering systems used by various cultures around the world and can be used as a reference for those wishing to create user-defined counter styles for CSS.
Editors
Marcos Caceres.
Internationalization Working Group- Family:
- Internationalization for HTML
Provides HTML/XHTML authors with best practices for developing internationalized content, supported by CSS, and focusing specifically on advice about specifying the language of content.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Internationalization for HTML
Provides HTML/XHTML authors with best practices for developing internationalized HTML supported by CSS to create pages for languages that use bidirectional text, such as Arabic, Hebrew, Persian, Thaana, Urdu, etc.
Editors
Richard Ishida.
Internationalization Working Group- Family:
- Internationalization for HTML
EARL
Complete
This document describes the requirements for the scope, design and features of the Evaluation and Report Language (EARL) 1.0. The Evaluation and Report Language is a standardized format to express test results. The primary motivation for developing this language is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor neutral and platform independent format. It will also provide reusable vocabulary for generic Web quality assurance and validation purposes.
Editors
Michael Squillace, Shadi Abou-Zahra.
Evaluation and Repair Tools Working Group- Family:
- EARL
This document describes the formal schema of the Evaluation and Report Language (EARL) 1.0. The Evaluation and Report Language is a standardized vocabulary to express test results. The primary motivation for developing this language is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor neutral and platform independent format. It also provides reusable vocabulary for generic quality assurance and validation purposes. While this document focuses on the technical details of the specification, a companion document [Guide] describes the motivations for EARL and provides a tutorial introduction to its use.
Editors
Shadi Abou-Zahra.
Evaluation and Repair Tools Working Group- Family:
- EARL
This document describes features that web authoring and quality assurance tools can incorporate, so that they support the evaluation of accessibility requirements, such as those defined by the Web Content Accessibility Guidelines (WCAG) 2.0. The main purpose of this document is to promote awareness of such tool features and to provide introductory guidance for tool developers regarding what kind of features they could provide in future implementations of their tools.
Editors
Carlos A. Velasco, Shadi Abou-Zahra.
Evaluation and Repair Tools Working Group- Family:
- EARL
The identification of resources on the Web by URI alone may not be sufficient, as other factors such as HTTP content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in RDF, to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by RFC 2616, as well as additional HTTP headers registered by IANA. These terms can also be used to record HTTPS exchanges.
Editors
Johannes Koch, Carlos A. Velasco, Philip Ackermann.
Evaluation and Repair Tools Working Group- Family:
- EARL
Add content here.
Editors
Carlos Iglesias.
Evaluation and Repair Tools Working Group- Family:
- EARL
This document is an introductory guide to the Evaluation and Report Language (EARL) 1.0. EARL is a vocabulary, the terms of which are defined across a set of specifications and technical notes, that is used to describe test results. The primary motivation for developing this vocabulary is to facilitate the exchange of test results between Web accessibility evaluation tools in a vendor-neutral and platform-independent format.
Editors
Carlos A. Velasco, Shadi Abou-Zahra.
Evaluation and Repair Tools Working Group- Family:
- EARL
This document is a specification for a vocabulary to represent Content in RDF. This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by Web accessibility evaluation tools to record a representation of the assessed Web content in an Evaluation And Report Language (EARL) 1.0 Schema evaluation report. The document contains introductory information on its usage and some examples.
Editors
Johannes Koch, Carlos A. Velasco, Philip Ackermann.
Evaluation and Repair Tools Working Group- Family:
- EARL
In progress
Accessibility metrics can extend the existing WCAG 2.0 conformance model to provide scores for the accessibility level of websites in more depth and detail. This Report provides considerations for validity, reliability, sensitivity, adequacy, and complexity as the main qualities of measuring web accessibility. The Report is a consolidated view of the outcomes of the Website Accessibility Metrics Online Symposium.
Editors
Markel Vigo, Giorgio Brajnik, Joshue O Connor.
Research and Development Working Group- Family:
- EARL
Data on the Web Best Practices
Complete
This document provides best practices related to the publication and usage of data on the Web designed to help support a self-sustaining ecosystem. Data should be discoverable and understandable by humans and machines. Where data is used in some way, whether by the originator of the data or by an external party, such usage should also be discoverable and the efforts of the data publisher recognized. In short, following these best practices will facilitate interaction between publishers and consumers.
Editors
Bernadette Farias Loscio, Caroline Burle, Newton Calegari.
Data on the Web Best Practices Working Group- Family:
- Data on the Web Best Practices
Datasets published on the Web are accessed and experienced by consumers in a variety of ways, but little information about these experiences is typically conveyed. Dataset publishers many times lack feedback from consumers about how datasets are used. Consumers lack an effective way to discuss experiences with fellow collaborators and explore referencing material citing the dataset. Datasets as defined by DCAT are a collection of data, published or curated by a single agent, and available for access or download in one or more formats. The Dataset Usage Vocabulary (DUV) is used to describe consumer experiences, citations, and feedback about the dataset from the human perspective.
Editors
Bernadette Farias Loscio, Eric Stephan, Sumit Purohit.
Data on the Web Best Practices Working Group- Family:
- Data on the Web Best Practices
This document provides a framework in which the quality of a dataset can be described, whether by the dataset publisher or by a broader community of users. It does not provide a formal, complete definition of quality, rather, it sets out a consistent means by which information can be provided such that a potential user of a dataset can make his/her own judgment about its fitness for purpose.
Editors
Riccardo Albertoni, Antoine Isaac.
Data on the Web Best Practices Working Group- Family:
- Data on the Web Best Practices
The Data on the Web Best Practices WG is faced with a substantial challenge in assessing the scope of its work, what problems it should prioritize and what level of advice is most appropriate for it to develop. A a significant amount of work therefore has gone in to collecting use cases from which requirements can be derived for all the WG's planned deliverables. The Use Case document is expected to evolve significantly in future but already today it provides a strong indication of the direction the WG is taking. Further use cases and comments are very welcome.
Editors
Deirdre Lee, Bernadette Farias Loscio, Phil Archer.
Data on the Web Best Practices Working Group- Family:
- Data on the Web Best Practices
Referrer Policy
In progress
This document describes how an author can set a referrer policy for documents they create, and the impact of such a policy on the referer HTTP header for outgoing requests and navigations.
Editors
Jochen Eisinger, Emily Stark.
Web Application Security Working Group- Family:
- Referrer Policy
Web Crypto
Complete
This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Key storage is provided for both temporary and permanent keys. Access to keying material is contingent on the same origin policy. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
Editors
Mark Watson.
Web Cryptography Working Group- Family:
- Web Crypto
This document consists of use cases for the Web Cryptography API and the Key Discovery API, expressed as scenarios along with illustrative code snippets.
Editors
Arun Ranganathan.
Web Cryptography Working Group- Family:
- Web Crypto
Webmention
Complete
Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it.
Editors
Aaron Parecki.
Social Web Working Group- Family:
- Webmention
Available in:
日本語CSS Round Display
In progress
CSS Round Display Level 1 describes CSS features to help authors build a Web page suitable for a round display. It extends CSS modules such as Media Queries, CSS Shapes, Borders, and Positioned Layout.
Editors
Jihye Hong.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Round Display
WebIDL
Complete
This document defines an interface definition language, Web IDL, that can be used to describe interfaces that are intended to be implemented in web browsers.
Editors
Cameron McCormack.
Web Platform Working Group- Family:
- WebIDL
This document defines the Java language binding for Web IDL, the interface definition language for the Web platform.
Editors
Cameron McCormack.
(historical) Web Applications Working Group- Family:
- WebIDL
MSE
Complete
This specification extends the HTMLMediaElement interface to allow JavaScript to generate media streams for playback.
Editors
Matthew Wolenetz, Jerry Smith, Mark Watson, Aaron Colwell, Adrian Bateman.
HTML Media Extensions Working Group- Family:
- MSE
This specification defines a Media Source Extensions byte stream format specification based on the ISO Base Media File Format.
Editors
Matthew Wolenetz, Jerry Smith, Mark Watson, Aaron Colwell, Adrian Bateman.
HTML Media Extensions Working Group- Family:
- MSE
This specification defines a Media Source Extensions byte stream format specification based on MPEG-2 Transport Streams.
Editors
Matthew Wolenetz, Jerry Smith, Mark Watson, Aaron Colwell, Adrian Bateman.
HTML Media Extensions Working Group- Family:
- MSE
This specification defines a Media Source Extensions byte stream format specification based on MPEG audio streams.
Editors
Matthew Wolenetz, Aaron Colwell.
HTML Media Extensions Working Group- Family:
- MSE
This specification defines the byte stream formats for use with the Media Source Extensions specification.
Editors
Matthew Wolenetz, Jerry Smith, Aaron Colwell.
HTML Media Extensions Working Group- Family:
- MSE
This specification defines a Media Source Extensions byte stream format specification based on the WebM container format.
Editors
Matthew Wolenetz, Jerry Smith, Aaron Colwell.
HTML Media Extensions Working Group- Family:
- MSE
This document defines the "webm" Initialization Data format for use with the Encrypted Media Extensions API.
HTML Media Extensions Working Group- Family:
- MSE
This document defines the stream format for using WebM content with the Encrypted Media Extensions API.
HTML Media Extensions Working Group- Family:
- MSE
Geolocation API
Complete
This specification defines an API that provides Web pages scripted access to geographical location information associated with the hosting device.
Editors
Andrei Popescu.
Geolocation Working Group- Family:
- Geolocation API
Available in:
日本語Vibration API
Complete
An API to control the device's vibrator.
Editors
Anssi Kostiainen.
Devices and Sensors Working Group- Family:
- Vibration API
Secure Contexts
In progress
This specification provides guidelines for user agent implementors and spec authors for implementing features whose properties dictate that they be exposed to the web only within a trustworthy environment.
Editors
Mike West.
Web Application Security Working Group- Family:
- Secure Contexts
Mixed Content
In progress
This specification describes how and why user agents disallow rendering and execution of content loaded over unencrypted or unauthenticated connections in the context of an encrypted and authenticated document.
Editors
Mike West.
Web Application Security Working Group- Family:
- Mixed Content
XProc
Complete
The XProc step library defines names and characteristics for a set of pipeline steps that every XProc processor is expected to support, as well as additional optional steps.
Editors
Norman Walsh, Alex Miłowski, Henry Thompson.
XML Processing Model Working Group- Family:
- XProc
XProc is an XML pipeline language; that is, a declarative dataflow language used to express steps required to process XML documents, coordinating operations such as querying, validation, inclusion, transformation and sorting.
Editors
Norman Walsh, Alex Miłowski, Henry Thompson.
XML Processing Model Working Group- Family:
- XProc
This specification defines several XML processor profiles, each of which fully determines a data model for any given XML document.
Editors
Henry Thompson, Norman Walsh, James Fuller.
XML Processing Model Working Group- Family:
- XProc
This document defines two new, optional templates designed to make it easier to construct documents within an XProc pipeline using values computed by that pipeline.
Editors
Norman Walsh.
XML Processing Model Working Group- Family:
- XProc
This specification describes the syntax and semantics of XProc: An XML Pipeline Language, a language for describing operations to be performed on XML documents.
An XML Pipeline specifies a sequence of operations to be performed on zero or more XML documents. Pipelines generally accept zero or more XML documents as input and produce zero or more XML documents as output. Pipelines are made up of simple steps which perform atomic operations on XML documents and constructs similar to conditionals, iteration, and exception handlers which control which steps are executed.
Editors
Norman Walsh, Alex Miłowski, Henry Thompson.
XML Processing Model Working Group- Family:
- XProc
This document contains requirements for the development of XML Processing Model and Language, which are intended to describe and specify the processing relationships between XML resources.
Editors
Dmitry Lenkov, Norman Walsh.
XML Core Working Group- Family:
- XProc
In progress
This document contains requirements on the development of XProc: An XML Pipeline Language Version 2.0. These requirements are focused primarily on making the language simpler and easier to use.
Editors
Alex Miłowski, James Fuller, Norman Walsh.
XML Processing Model Working Group- Family:
- XProc
This document contains requirements for the development of an XML Processing Model and Language, which are intended to describe and specify the processing relationships between XML resources.
Editors
Alex Miłowski.
UNKNOWN WORKING GROUP- Family:
- XProc
XInclude
Complete
This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references).
Editors
Jonathan Marsh, David Orchard, Daniel Veillard, Norman Walsh.
XML Core Working Group- Family:
- XInclude
Editors
Norman Walsh.
XML Core Working Group- Family:
- XInclude
This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references).
Editors
Jonathan Marsh, David Orchard, Daniel Veillard.
XML Core Working Group- Family:
- XInclude
Battery Status API
In progress
This specification defines a new DOM event type that provides information about the battery status of the hosting device and associated auxiliary devices.
Editors
Anssi Kostiainen, Mounir Lamouri.
Devices and Sensors Working Group- Family:
- Battery Status API
Subresource Integrity
Complete
This document defines a mechanism by which user agents may verify that a fetched resource has been delivered without unexpected manipulation.
Editors
Devdatta Akhawe, Frederik Braun, Francois Marier, Joel Weinberger.
Web Application Security Working Group- Family:
- Subresource Integrity
Web Security UI
Complete
This specification defines guidelines and requirements for the presentation and communication of Web security context information to end-users.
Editors
Thomas Roessler, Anil Saldhana.
Web Security Context Working Group- Family:
- Web Security UI
This Note refines the objectives for the Web Security Context Working Group deliverables. It elaborates upon the group's Charter [WSC-CHARTER] to explain what the group aims to achieve, what technologies may be used and how technical proposals will be evaluated. This elaboration is limited to the group's technical work and does not cover additional activities the group intends to engage in, such as ongoing outreach and education.
This Note also includes an initial collection of use cases that the group expects will drive its technical work.
Since this Note discusses the assumptions, goals, and processes the group will use to develop its recommendations, the intended audience is similiar to that of the charter of the Working Group; group members, the W3C community, developers of web user agents, web content providers (server administrators), and parties interested and engaged in what the Web Security Context Working Group's plans and directions are. It is explicitly not targeted at the presumed beneficiaries of the group's work, the users of the web, and it is not expected that an average user would be able to read this document and understand it.
Editors
Tyler Close.
Web Security Context Working Group- Family:
- Web Security UI
This Note includes threat trees used to analyze the threats that the [WSC-XIT] responds to. It is a companion document to [WSC-USECASES].
Editors
Thomas Roessler.
Web Security Context Working Group- Family:
- Web Security UI
In progress
This document defines directives for the Content Security Policy mechanism to declare a set of input protections for a web resource's user interface, defines a non-normative set of heuristics for Web user agents to implement these input protections, and a reporting mechanism for when they are triggered.
Editors
Brad Hill.
Web Application Security Working Group- Family:
- Web Security UI
Digital Publishing
Complete
This document, “Digital Publishing and Accessibility in W3C Documents” describes how W3C guidelines (including but not limited to [WCAG20], [ATAG20], [UAAG20], and [WAI-ARIA]) and their principles, guidelines, and success criteria can be applied to the needs of Digital Publishing. It provides informative guidance, but does not set requirements.
Editors
Deborah Kaplan, Charles LaPierre.
Digital Publishing Interest Group- Family:
- Digital Publishing
The Metadata Task Force of the Digital Publishing Interest Group conducted a series of interviews with representatives of various sectors and roles within the publishing ecosystem. This Note includes a write-up of those interviews, documents in detail the issues that were raised, and provides general conclusions on where the W3C can contribute to the general advancement of metadata usage in the Digital Publishing Domain.
Editors
Bill Kasdorf, Madi Solomon, Ivan Herman.
Digital Publishing Interest Group- Family:
- Digital Publishing
In progress
This document documents CSS features needed by the digital publishing community, as determined by the W3C Digital Publishing Interest Group.
Editors
Dave Cramer.
Digital Publishing Interest Group- Family:
- Digital Publishing
CSS Snapshot
Complete
CSS 2.1 is derived from and is intended to replace CSS2. It supports media-specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. It also supports content positioning, table layout, features for internationalization and some properties related to user interface. CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented. But most of all CSS 2.1 represents a "snapshot" of CSS usage: it consists of all CSS features that are implemented interoperably at the date of publication of the Recommendation.
Editors
Bert Bos, Tantek Çelik, Ian Hickson, Håkon Wium Lie.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Snapshot
Available in:
日本語In progress
CSS is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications). CSS 2.2 is the second revision of level 2 of CSS. It corrects a few errors in CSS 2.1.
Editors
Bert Bos.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Snapshot
CSS Device Adaptation
In progress
This specification provides a way for an author to specify, in CSS, the size, zoom factor, and orientation of the viewport that is used as the base for the initial containing block.
Editors
Rune Lillesveen, Florian Rivoal, Matt Rakow.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Device Adaptation
Tabular Data
Complete
A large percentage of the data published on the Web is tabular data, commonly published as comma separated values (CSV) files. The CSV on the Web Working Group aim to specify technologies that provide greater interoperability for data dependent applications on the Web when working with tabular datasets comprising single or multiple files using CSV, or similar, format.
Editors
Jeremy Tandy, Davide Ceolin, Eric Stephan.
CSV on the Web Working Group- Family:
- Tabular Data
The CSV on the Web Working Group has developed standard ways to express useful metadata about CSV files and other kinds of tabular data. This primer takes you through the ways in which these standards work together.
Editors
Jeni Tennison.
CSV on the Web Working Group- Family:
- Tabular Data
Tabular data is often contained within HTML in the form of HTML table elements. This document describes a means of identifying such tables and extracting annotated tabular data from HTML tables.
Editors
Gregg Kellogg.
CSV on the Web Working Group- Family:
- Tabular Data
Validation, conversion, display and search of tabular data on the web requires additional metadata that describes how the data should be interpreted. This document defines a vocabulary for metadata that annotates tabular data. This can be used to provide metadata at various levels, from collections of data from CSV documents and how they relate to each other down to individual cells within a table.
Editors
Jeni Tennison, Gregg Kellogg.
CSV on the Web Working Group- Family:
- Tabular Data
This document defines the procedures and rules to be applied when mapping tabular data into JSON. Tabular data may be complemented with metadata annotations that describe its structure, the meaning of its content and how it may form part of a collection of interrelated tabular data. This document specifies the effect of this metadata on the resulting JSON.
Editors
Jeremy Tandy, Ivan Herman.
CSV on the Web Working Group- Family:
- Tabular Data
This document defines the procedures and rules to be applied when mapping tabular data into RDF. Tabular data may be complemented with metadata annotations that describe its structure, the meaning of its content and how it may form part of a collection of interrelated tabular data. This document specifies the effect of this metadata on the resulting RDF.
Editors
Jeremy Tandy, Ivan Herman, Gregg Kellogg.
CSV on the Web Working Group- Family:
- Tabular Data
Tabular data is routinely transferred on the web as "CSV", but the definition of "CSV" in practice is very loose. This document outlines a basic data model or infoset for tabular data and metadata about that tabular data. It also contains some non-normative information about a best practice syntax for tabular data, for mapping into that data model, to contribute to the standardisation of CSV syntax by IETF. Various methods of locating metadata are also provided.
Editors
Jeni Tennison, Gregg Kellogg.
CSV on the Web Working Group- Family:
- Tabular Data
UAAG
Complete
This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities. User agents include browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable.
In addition to helping developers of browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities.
The "User Agent Accessibility Guidelines 2.0" (UAAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).
Editors
James Allan, Greg Lowney, Kimberly Patch, Jeanne F Spellman.
User Agent Accessibility Guidelines Working Group- Family:
- UAAG
This document provides explanation of the intent of UAAG 2.0 success criteria, examples of implementation of the UAAG 2.0 guidelines, best practice recommendations and additional resources for the guidelines.
Editors
James Allan, Greg Lowney, Kimberly Patch, Jeanne F Spellman.
User Agent Accessibility Guidelines Working Group- Family:
- UAAG
This document provides techniques for satisfying the checkpoints defined in "User Agent Accessibility Guidelines 1.0" [UAAG10]. These techniques address key aspects of the accessibility of user interfaces, content rendering, application programming interfaces (APIs), and languages such as the Hypertext Markup Language (HTML), Cascading Style Sheets (CSS) and the Synchronized Multimedia Integration Language (SMIL).
The techniques listed in this document are not required for conformance to the Guidelines. These techniques are not necessarily the only way of satisfying the checkpoint, nor are they a definitive set of requirements for satisfying a checkpoint.
Editors
Ian Jacobs, Jon Gunderson, Eric Hansen.
User Agent Accessibility Guidelines Working Group- Family:
- UAAG
This document provides guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). User agents include HTML browsers and other types of software that retrieve and render Web content. A user agent that conforms to these guidelines will promote accessibility through its own user interface and through other internal facilities, including its ability to communicate with other technologies (especially assistive technologies). Furthermore, all users, not just users with disabilities, should find conforming user agents to be more usable.
In addition to helping developers of HTML browsers and media players, this document will also benefit developers of assistive technologies because it explains what types of information and control an assistive technology may expect from a conforming user agent. Technologies not addressed directly by this document (e.g., technologies for braille rendering) will be essential to ensuring Web access for some users with disabilities.
Editors
Ian Jacobs, Jon Gunderson, Eric Hansen.
User Agent Accessibility Guidelines Working Group- Family:
- UAAG
Available in:
françaisIn progress
This First Public Working Draft outlines the requirements that the User Agent Accessibility Guidelines Working Group (UAWG) has set for development of User Agent Accessibility Guidelines 2.0 (UAAG 2.0). These requirements are based on feedback from the use of UAAG 1.0 and will be used to determine if the UAWG has met its goals as UAAG 2.0 advances through the W3C Recommendation Track Process.
Editors
Jim Allan, Jan Richards.
User Agent Accessibility Guidelines Working Group- Family:
- UAAG
CSS Custom Properties for Cascading Variables
In progress
This module contains features of CSS relating to variables. A variable is a type of value that is accepted by all properties and several properties can share the same variable.
Editors
Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Custom Properties for Cascading Variables
CSS Will Change
In progress
The 'will-change' property allows an author to inform the UA what kinds of style changes are likely to be made to an element, e.g., as a result of animations or other dynamic effects. This allows the UA to optimize how it handles the element.
Editors
Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Will Change
Upgrade Insecure Requests
In progress
This document defines a mechanism which allows authors to instruct a user agent to upgrade a priori insecure resource requests to secure transport before fetching them.
Editors
Mike West.
Web Application Security Working Group- Family:
- Upgrade Insecure Requests
ATAG
Complete
Implementing ATAG 2.0 is an essential guide to understanding and using "Authoring Tool Accessibility Guidelines 2.0" [ATAG20]. Although the normative definitions and requirements for ATAG 2.0 can all be found in the ATAG 2.0 document itself, the concepts and provisions may be new to some people. Implementing ATAG 2.0 provides a non-normative extended commentary on each guideline and each success criterion to help readers better understand the intent and how the guidelines and success criteria work together. It also provides examples that the Working Group has identified for each success criterion.
Editors
Jan Richards, Jeanne F Spellman, Jutta Treviranus.
Authoring Tool Accessibility Guidelines Working Group- Family:
- ATAG
This specification provides guidelines for designing Web content authoring tools that are more accessible for people with disabilities. An authoring tool that conforms to these guidelines will promote accessibility by providing an accessible user interface to authors with disabilities as well as enabling, supporting, and promoting the production of accessible Web content by all authors.
The "Authoring Tool Accessibility Guidelines 2.0" (ATAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).
Editors
Jan Richards, Jeanne F Spellman, Jutta Treviranus.
Authoring Tool Accessibility Guidelines Working Group- Family:
- ATAG
Available in:
简体中文This document provides information to authoring tool developers who wish to satisfy the checkpoints of "Authoring Tool Accessibility Guidelines 1.0" [ATAG10]. It includes suggested techniques, sample strategies in deployed tools, and references to other accessibility resources (such as platform-specific software accessibility guidelines) that provide additional information on how a tool may satisfy each checkpoint.
This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI).
Editors
Jutta Treviranus, Charles McCathieNevile, Jan Richards, Gregory Rosmaita.
Authoring Tool Accessibility Guidelines Working Group- Family:
- ATAG
This specification provides guidelines for Web authoring tool developers. Its purpose is two-fold: to assist developers in designing authoring tools that produce accessible Web content and to assist developers in creating an accessible authoring interface.
Authoring tools can enable, encourage, and assist users ("authors") in the creation of accessible Web content through prompts, alerts, checking and repair functions, help files and automated tools. It is just as important that all people be able to author content as it is for all people to have access to it. The tools used to create this information must therefore be accessible themselves. Adoption of these guidelines will contribute to the proliferation of Web content that can be read by a broader range of readers and authoring tools that can be used by a broader range of authors.
This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative (WAI).
Editors
Jutta Treviranus, Charles McCathieNevile, Ian Jacobs, Jan Richards.
Authoring Tool Accessibility Guidelines Working Group- Family:
- ATAG
CSS Page Floats
In progress
CSS Page Floats describes how to use CSS to place "floats" at the top or bottom of certain areas. This feature has traditionally been used in print publications in which figures and photos are moved to the top or bottom of columns or pages.
Editors
Johannes Wilm.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Page Floats
SCXML
Complete
This document describes SCXML, or the "State Chart extensible Markup Language". SCXML provides a generic state-machine based execution environment based on CCXML and Harel State Tables.
Editors
James Barnett, Rahul Akolkar, RJ Auburn, Michael Bodell, Daniel Burnett, Jerry Carter, Scott McGlashan, Torbjörn Lager, Marc Helbing, Rafah Hosn, T.V. Raman, Klaus Reifenrath, Noam Rosenthal, Johan Roxendal.
Voice Browser Working Group- Family:
- SCXML
This document describes the XPath Data Model for SCXML. This data model allows SCXML state charts to use XML as their data representation, and to manipulate it with XPath. For more details on data models, see the SCXML specification.
The category of this specification should be "Voice" but the original SCXML specification is included in "Declarative Web Applications" as well. So it would make sense to include this Note in that category as well.
Editors
James Barnett, Rahul Akolkar, RJ Auburn, Michael Bodell, Daniel Burnett, Jerry Carter, Scott McGlashan, Torbjörn Lager, Marc Helbing, Rafah Hosn, T V Raman, Klaus Reifenrath, Noam Rosenthal, Johan Roxendal.
Voice Browser Working Group- Family:
- SCXML
This document describes the DOM Event I/O Processor for SCXML. This event processor allows SCXML state machines to communicate with external entities via DOM Events. For more details on Event I/O Processors, see the SCXML specification.
The category of this specification should be "Voice" but the original SCXML specification is included in "Declarative Web Applications" as well. So it would make sense to include this Note in that category as well.
Editors
James Barnett, Rahul Akolkar, RJ Auburn, Michael Bodell, Daniel Burnett, Jerry Carter, Scott McGlashan, Torbjörn Lager, Marc Helbing, Rafah Hosn, T V Raman, Klaus Reifenrath, Noam Rosenthal, Johan Roxendal.
Voice Browser Working Group- Family:
- SCXML
XML Signature
Complete
XML Signature 2.0 evolves the transform model of XML Signature to enable easier and more efficient implementations of the specification.
Editors
Donald Eastlake, Joseph Reagle, David Solo, Frederick Hirsch, Thomas Roessler, Kelvin Yiu, Pratik Datta, Scott Cantor.
XML Security Working Group- Family:
- XML Signature
Add content here.
Editors
Frederick Hirsch.
XML Security Working Group- Family:
- XML Signature
Editors
Frederick Hirsch.
XML Security Working Group- Family:
- XML Signature
Add content here.
Editors
Frederick Hirsch, Thomas Roessler.
XML Security Working Group- Family:
- XML Signature
This document defines a streamable profile of XPath 1.0 suitable for use with XML Signature 2.0.
Editors
Pratik Datta, Frederick Hirsch, Meiko Jensen.
XML Security Working Group- Family:
- XML Signature
This document outlines use cases, requirements and design choices for XML Security 2.0, specifically Canonical XML 2.0 and XML Signature 2.0. It includes a proposed simplification of the XML Signature Transform mechanism, intended to enhance security, performance, streamability and to ease adoption.
Editors
Frederick Hirsch, Pratik Datta.
XML Security Working Group- Family:
- XML Signature
This document serves to publish RELAX NG schemas for XML Security specifications, including XML Signature 1.1, and XML Signature Properties.
Editors
Murata Makoto, Frederick Hirsch.
XML Security Working Group- Family:
- XML Signature
Add content here.
Editors
Frederick Hirsch, Pratik Datta.
XML Security Working Group- Family:
- XML Signature
Add content here.
Editors
Donald Eastlake, Joseph Reagle, David Solo, Frederick Hirsch, Magnus Nyström, Thomas Roessler, Kelvin Yiu.
XML Security Working Group- Family:
- XML Signature
Editors
Frederick Hirsch, Pratik Datta.
XML Security Working Group- Family:
- XML Signature
Add content here.
Editors
Frederick Hirsch, Pratik Datta.
UNKNOWN WORKING GROUP- Family:
- XML Signature
This document defines interoperability test cases for Canonical XML 1.1 [XML-C14N1.1] and XML Signature Syntax and Processing, Second Edition [XMLDSIG2]. The changes tested include C14N11 handling of attributes in the XML namespace, including xml:id and xml:base, appropriate C14N11 nodeset to octet stream transform processing, modifications to RFC 3986 dot segment processing for C14N11, and RFC 4514 string encoding of ../distinguished Names. The tests include standalone C14N11 tests as well as tests integrated with XML signature generation and validation. This document also includes earlier test cases used in XML Signature [XMLDSIG] for regression testing.
Editors
Juan Carlos Cruellas, Konrad Lanz, Sean Mullan.
XML Security Specifications Maintenance Working GroupXML Security Working Group
- Family:
- XML Signature
This technical note describes how to use the XML Digital Signature Recommendation [XMLDSIG] in a way consistent with the present (fall 2006) XML environment. In particular, this note takes into account the recent xml:id Version 1.0 [XMLID] Recommendation, and work in progress towards a Canonical XML Version 1.1 [C14N11] Recommendation.
This note suggests constraints on the use of XML Signature, and relies on extension points present in the XML Digital Signature Recommendation. This note does not override any aspect of that Recommendation.
Editors
Thomas Roessler.
XML Core Working Group- Family:
- XML Signature
The XML Key Management Specification (XKMS 2.0) [XKMS] aims at providing a PKI independent interface to key management. XKMS services comprise discovery and validation of keys as well as support for certain aspects of the key life cycle management, including registration, reissuance and revocation.
XKMS employs XML Signature [XMLSIG] for the purpose of providing message security in the form of authentication and integrity. In addition, XKMS is based on the use of the <ds:KeyInfo> element as a means of transporting key information used as templates for the various operations it specifies.
This technical note addresses some of the issues related to the use of XKMS in conjunction with PGP [PGP].
Editors
Tommy Lindberg, José Kahan.
UNKNOWN WORKING GROUP- Family:
- XML Signature
The XML Key Management Specification (XKMS 2.0) is a W3C Recommendation that specifies protocols for ../distributing and registering public keys.
The XML Key Management Service (XKMS) Working Group has defined a Web Service to handle conventional PKI (public-key infrastructure) functions such as registration, revocation and status, as well as related functions such as retrieval.
This note provides a sample Web Services Description Language (WSDL) 1.1 description for an XKMS service. It is intended that XKMS developers use this as a "first draft" for developing their own version. Conversion to WSDL 2.0 should be fairly straightforward, once that specification completes its Last Call.
Editors
Rich Salz, Yunhao Zhang.
UNKNOWN WORKING GROUP- Family:
- XML Signature
[2]This document specifies protocol bindings with security characteristics for the XML Key Management Specification (XKMS).
Editors
Phillip Hallam-Baker, Shivaram Mysore.
UNKNOWN WORKING GROUP- Family:
- XML Signature
Available in:
français[2]This document specifies protocols for ../distributing and registering public keys, suitable for use in conjunction with the W3C Recommendations for XML Signature [XML-SIG] and XML Encryption [XML-Enc]. The XML Key Management Specification (XKMS) comprises two parts — the XML Key Information Service Specification (X-KISS) and the XML Key Registration Service Specification (X-KRSS).
Editors
Phillip Hallam-Baker, Shivaram Mysore.
UNKNOWN WORKING GROUP- Family:
- XML Signature
This document lists the design principles, scope and requirements for XML Key Management specifications and trust server key management implementations. It includes requirements as they relate to the key management syntax, processing, security and coordination with other standards activities.
Editors
Frederick Hirsch, Mike Just.
UNKNOWN WORKING GROUP- Family:
- XML Signature
This document specifies an XML Signature "decryption transform" that enables XML Signature applications to ../distinguish between those XML Encryption structures that were encrypted before signing (and must not be decrypted) and those that were encrypted after signing (and must be decrypted) for the signature to validate.
Editors
Merlin Hughes, Takeshi Imamura, Hiroshi Maruyama.
XML Security Working Group- Family:
- XML Signature
Available in:
françaisXML Signature [XML-DSig] recommends a standard means for specifying information content to be digitally signed and for representing the resulting digital signatures in XML. Some applications require the ability to specify a subset of a given XML document as the information content to be signed. The XML Signature specification meets this requirement with the XPath transform. However, this transform can be difficult to implement efficiently with existing technologies. This specification defines a new XML Signature transform to facilitate the development of efficient document subsetting implementations that interoperate under similar performance profiles.
Editors
John Boyer, Merlin Hughes, Joseph Reagle.
XML Security Working Group- Family:
- XML Signature
Available in:
españolHCLS
Complete
This document describes a consensus among participating stakeholders in the Health Care and the Life Sciences domain on the description of datasets using the Resource Description Framework (RDF). This specification meets key functional requirements, reuses existing vocabularies to the extent that it is possible, and addresses elements of data description, versioning, provenance, discovery, exchange, query, and retrieval.
Editors
Alasdair Gray, M. Scott Marshall, Michel Dumontier.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
Editors
Paolo Ciccarese, Tudor Groza.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
Editors
Alexandre Passant, Paolo Ciccarese.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
Editors
Alexandre Passant.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
Editors
Paolo Ciccarese.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
The prototype we describe is a biomedical knowledge base, constructed for a demonstration at Banff WWW2007 , that integrates 15 ../distinct data sources using currently available Semantic Web technologies such as the W3C standard Web Ontology Language [OWL] and Resource Description Framework [RDF]. This report outlines which resources were integrated, how the knowledge base was constructed using free and open source triple store technology, how it can be queried using the W3C Recommended RDF query language SPARQL [SPARQL], and what resources and inferences are involved in answering complex queries. While the utility of the knowledge base is illustrated by identifying a set of genes involved in Alzheimer's Disease, the approach described here can be applied to any use case that integrates data from multiple domains.
Editors
M. Scott Marshall, Eric Prud'hommeaux.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
One of the challenges facing Semantic Web for Health Care and Life Sciences is that of converting relational databases into Semantic Web format. The issues and the steps involved in such a conversion have not been well documented. To this end, we have created this document to describe the process of converting SenseLab databases into OWL. SenseLab is a collection of relational (Oracle) databases for neuroscientific research. The conversion of these databases into RDF/OWL format is an important step towards realizing the benefits of Semantic Web in integrative neuroscience research. This document describes how we represented some of the SenseLab databases in Resource Description Framework (RDF) and Web Ontology Language (OWL), and discusses the advantages and disadvantages of these representations. Our OWL representation is based on the reuse and extension of existing standard OWL ontologies developed in the biomedical ontology communities. The purpose of this document is to share our implementation experience with the community.
Editors
Matthias Samwald, Kei-Hoi Cheung.
Semantic Web Health Care and Life Sciences Interest Group- Family:
- HCLS
IndieUI
In progress
Defines a set of preferences that users can choose to expose to web applications, and an API for user agents to access the preferences and listen for changes. Web applications can use this information to optimize the presentation without a requirement to target a specific device, operating system, or locale.
Editors
James Craig, Michael Cooper.
Independent User Interface (Indie UI) Working Group- Family:
- IndieUI
An abstraction between device-specific user interaction events and inferred user intent such as scroll, activate, etc. This provides an intermediate layer between device- and modality-specific user interaction events, and the basic user interface functionality used by Web applications.
Editors
James Craig, Michael Cooper.
Independent User Interface (Indie UI) Working Group- Family:
- IndieUI
Outlines the requirements that the IndieUI Working Group has set for development of IndieUI: Events 1.0 and IndieUI: User Context 1.0.
Editors
Michael Cooper.
Independent User Interface (Indie UI) Working Group- Family:
- IndieUI
CSS Template Layout
Complete
CSS is a simple, declarative language for creating style sheets that specify the rendering of HTML and other structured documents. This specification is part of level 3 of CSS (“CSS3”) and contains features to describe layouts at a high level, meant for tasks such as the positioning and alignment of “widgets” in a graphical user interface or the layout grid for a page or a window, in particular when the desired visual order is different from the order of the elements in the source document. Other CSS3 modules contain properties to specify fonts, colors, text alignment, list numbering, tables, etc.
The features in this module are described together for easier reading, but are usually not implemented as a group. CSS3 modules often depend on other modules or contain features for several media types. Implementers should look at the various “profiles” of CSS, which list consistent sets of features for each type of media.
Editors
Bert Bos, César Acebal.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Template Layout
Web MIDI API
In progress
This specification defines an API supporting the MIDI protocol, enabling web applications to enumerate and select MIDI input and output devices on the client system and send and receive MIDI messages. It is intended to enable non-music MIDI applications as well as music ones, by providing low-level access to the MIDI devices available on the users' systems.
Editors
Chris Wilson, Jussi Kalliokoski.
Audio Working Group- Family:
- Web MIDI API
RDFa
Complete
RDFa Core is a specification for attributes to express structured data in any markup language. The embedded data already available in the markup language (e.g., XHTML) is reused by the RDFa markup, so that publishers don't need to repeat significant data in the document content.
Editors
Ben Adida, Mark Birbeck, Shane McCarron, Ivan Herman.
RDFa Working Group- Family:
- RDFa
Available in:
日本語RDFa Core 1.1 defines attributes and syntax for embedding semantic markup in Host Languages. This document defines one such Host Language. This language is a superset of XHTML 1.1, integrating the attributes as defined in RDFa Core 1.1.
Editors
Shane McCarron.
RDFa Working Group- Family:
- RDFa
Available in:
日本語This specification defines rules and guidelines for adapting the RDFa Core 1.1 and RDFa Lite 1.1 specifications for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules.
Editors
Manu Sporny.
RDFa Working Group- Family:
- RDFa
Available in:
日本語HTML and RDFa (Resource Description Framework in Attributes) provides a set of markup attributes to augment visual information on the Web with machine-readable hints. In this Primer, we show how to express data using RDFa in HTML, and in particular how to mark up existing human-readable Web page content to express machine-readable data.
Editors
Ivan Herman, Ben Adida, Manu Sporny, Mark Birbeck.
RDFa Working Group- Family:
- RDFa
RDFa Lite is a small subset of RDFa consisting of a few attributes that may be applied to most simple to moderate structured data markup tasks. While it is not a complete solution for advanced markup tasks, it does provide a good entry point for beginners.
Editors
Manu Sporny.
RDFa Working Group- Family:
- RDFa
CSS Exclusions
In progress
The module defines (1) properties to assign a shape (circle or polygon) to CSS boxes, to control the line length more precisely than with margins; (2) properties to define how text in other boxes wraps around such a shaped box; and (3) properties to turn an absolutely positioned box into an exclusion, causing text to wrap around it, too.
Editors
Rossen Atanassov, Vincent Hardy, Alan Stearns.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Exclusions
Compositing and Blending
In progress
Compositing describes how shapes of different elements are combined into a single image by overlaying, masking, blending, etc. The specification also defines a syntax for using compositing in CSS.
Editors
Rik Cabanier, Nikos Andronikos.
SVG Working GroupCascading Style Sheets (CSS) Working Group
- Family:
- Compositing and Blending
CSS Regions
In progress
The CSS Regions specification defines CSS properties to ../distribute the content of one element over multiple, disconnected regions, such as the regions defined by CSS Grid Layout.
Editors
Rossen Atanassov, Alan Stearns.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Regions
CSS Line Grid
In progress
This module contains CSS features for aligning content to a baseline grid.
Editors
Elika Etemad, Koji Ishii, Alan Stearns.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Line Grid
CSS Masking
In progress
CSS Masking provides two means for partially or fully hiding portions of visual elements: masking and clipping. Masking describes how to use another graphical element or image as a luminance or alpha mask. Clipping describes the visible region of visual elements. This module defines faetures for both SVG and CSS.
Editors
Dirk Schulze, Brian Birtles, Tab Atkins Jr..
SVG Working GroupCascading Style Sheets (CSS) Working Group
- Family:
- CSS Masking
Wake lock
Complete
This document illustrates the use cases a mechanism to control the power-saving state of a device would enable on the Web platform.
Editors
Marcos Caceres, Natasha Rooney, Dominique Hazaël-Massieux.
Web and Mobile Interest Group- Family:
- Wake lock
RDF
Complete
The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. This primer is designed to provide the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and shows concrete examples of the use of RDF.
Editors
Guus Schreiber, Yves Raimond.
RDF Working Group- Family:
- RDF
Available in:
portuguêsThis document describes a precise semantics for the Resource Description Framework 1.1 and RDF Schema. It defines a number of ../distinct entailment regimes and corresponding patterns of entailment. It is part of a suite of documents which comprise the full specification of RDF 1.1.
Editors
Patrick Hayes, Peter Patel-Schneider.
RDF Working Group- Family:
- RDF
Available in:
日本語RDF defines the concept of RDF datasets, a structure composed of a ../distinguished RDF graph and zero or more named graphs, being pairs comprising an IRI or blank node and an RDF graph. While RDF graphs have a formal model-theoretic semantics that determines what arrangements of the world make an RDF graph true, no agreed formal semantics exists for RDF datasets. This document presents some issues to be addressed when defining a formal semantics for datasets, as they have been discussed in the RDF 1.1 Working Group, and specify several semantics in terms of model theory, each corresponding to a certain design choice for RDF datasets.
Editors
Antoine Zimmermann.
RDF Working Group- Family:
- RDF
The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. This document is intended to provide the reader with a summary of changes to RDF introduced in RDF version 1.1.
Editors
David Wood.
RDF Working Group- Family:
- RDF
The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web.
This document defines an XML syntax for RDF called RDF/XML in terms of Namespaces in XML, the XML Information Set and XML Base. The formal grammar for the syntax is annotated with actions generating triples of the RDF graph as defined in RDF Concepts and Abstract Syntax. The triples are written using the N-Triples RDF graph serializing format which enables more precise recording of the mapping in a machine processable form. The mappings are recorded as tests cases, gathered and published in RDF Test Cases.
Editors
Fabien Gandon, Guus Schreiber.
RDF Working Group- Family:
- RDF
Available in:
日本語The Resource Description Framework (RDF) is a framework for representing information in the Web. RDF 1.1 Concepts and Abstract Syntax defines an abstract syntax (a data model) which serves to link all RDF-based languages and specifications. The abstract syntax has two key data structures: RDF graphs are sets of subject-predicate-object triples, where the elements may be IRIs, blank nodes, or datatyped literals. They are used to express descriptions of resources. RDF datasets are used to organize collections of RDF graphs, and comprise a default graph and zero or more named graphs. This document also introduces key concepts and terminology, and discusses datatyping and the handling of fragment identifiers in IRIs within RDF graphs.
Editors
Richard Cyganiak, David Wood, Markus Lanthaler.
RDF Working Group- Family:
- RDF
The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web.
Editors
Eric Prud'hommeaux, Gavin Carothers.
RDF Working Group- Family:
- RDF
Available in:
日本語This document defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle format.
Editors
Gavin Carothers, Andy Seaborne.
RDF Working Group- Family:
- RDF
The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This specification describes how to use RDF to describe RDF vocabularies. This specification defines a vocabulary for this purpose and defines other built-in RDF vocabulary initially specified in the RDF Model and Syntax Specification.
Editors
Dan Brickley, Ramanathan Guha.
RDF Working Group- Family:
- RDF
N-Quads is a line-based, plain text format for encoding an RDF dataset.
Editors
Gavin Carothers.
RDF Working Group- Family:
- RDF
Available in:
日本語This document lists the test suites and implementation reports for RDF 1.1 Semantics as well as the various serialization formats.
Editors
Gregg Kellogg, Markus Lanthaler.
RDF Working Group- Family:
- RDF
N-Triples is a line-based, plain text format for encoding an RDF graph.
Editors
Gavin Carothers, Andy Seaborne.
RDF Working Group- Family:
- RDF
Available in:
日本語The Resource Description Framework (RDF) is a framework for representing information in the Web. This document defines a textual syntax for RDF called RDF/JSON that allows an RDF graph to be completely written in a form compatible with the JavaScript Object Notation (JSON) [RFC4627] and alternative to the one recommended in JSON-LD [JSON-LD]. The syntax defined in this document should not be used unless there is a specific reason to do so. Use of JSON-LD is recommended.
Editors
Ian Davis, Thomas Steiner, Arnaud Le Hors.
RDF Working Group- Family:
- RDF
The Linked Data Glossary contains terms defined and used to describe Linked Data, and its associated vocabularies and best practices related to publishing structured data on the Web using open Web standards.
Editors
Bernadette Hyland, Ghislain Auguste Atemezing, Michael Pendleton, Biplav Srivastava.
Government Linked Data Working Group- Family:
- RDF
Add content here.
Editors
Jie Bao, Sandro Hawke, Boris Motik, Peter Patel-Schneider, Axel Polleres.
Rule Interchange Format Working GroupOWL Working Group
- Family:
- RDF
Available in:
日本語This document describes best practice recipes for publishing vocabularies or ontologies on the Web (in RDF Schema or OWL). The features of each recipe are described in detail, so that vocabulary designers may choose the recipe best suited to their needs. Each recipe introduces general principles and an example configuration for use with an Apache HTTP server (which may be adapted to other environments). The recipes are all designed to be consistent with the architecture of the Web as currently specified, although the associated example configurations have been kept intentionally simple.
Editors
Diego Berrueta, Jon Phipps.
Semantic Web Deployment Working Group- Family:
- RDF
Available in:
françaisIn Semantic Web languages, such as RDF and OWL, a property is a binary relation: it is used to link two individuals or an individual and a value. However, in some cases, the natural and convenient way to represent certain concepts is to use relations to link an individual to more than just one individual or value. These relations are called n-ary relations. For example, we may want to represent properties of a relation, such as our certainty about it, severity or strength of a relation, relevance of a relation, and so on. Another example is representing relations among multiple individuals, such as a buyer, a seller, and an object that was bought when describing a purchase of a book. This document presents ontology patterns for representing n-ary relations in RDF and OWL and discusses what users must consider when choosing these patterns.
Editors
Natasha Noy, Alan Rector.
Semantic Web Best Practices and Deployment Working Group- Family:
- RDF
Available in:
русскийDomain models play a central role throughout the software development cycle, from requirements analysis to design, through implementation and beyond. As such, great progress has been made in the consistent use of models throughout this process. Modern software development tools with support for the UML and code generation as well as Model-Driven Architectures allow for developers to synchronize and verify technical implementation with user requirements using models. However, the reusability of domain models is often limited because they are, by definition, domain specific and only take into consideration abstractions needed to make possible a solution within the confines of their own individual problem space. But the Web is broader than that and provides a multidimensional solution space capable of referencing an almost limitless set of domains. While much of our software becomes increasingly embedded in the Web, our development processes do not fully exploit the potential of model reuse from the Web yet. This note therefore introduces Semantic Web languages such as RDF Schema and OWL, and shows how they can be used in tandem with mainstream object-oriented languages. We show that the Semantic Web can serve as a platform on which domain models can be created, shared and reused.
Editors
Holger Knublauch, Daniel Oberle, Philip Tetlow, Evan Wallace.
Semantic Web Best Practices and Deployment Working Group- Family:
- RDF
Available in:
русскийThe Resource Description Framework (RDF) is a model developed by the W3C for representing information about resources in the World Wide Web. Topic Maps is a standard for knowledge integration developed by the ISO. This document contains a survey of existing proposals for integrating RDF and Topic Maps data and is intended to be a starting point for establishing standard guidelines for RDF/Topic Maps interoperability.
Editors
Steve Pepper, Fabio Vitali, Lars Marius Garshol, Nicola Gessa, Valentina Presutti.
Semantic Web Best Practices and Deployment Working Group- Family:
- RDF
This document addresses the issue of using classes as property values in OWL and RDF Schema. It is often convenient to put a class (e.g., ) as a property value (e.g., topic or book subject) when building an ontology. While OWL Full and RDF Schema do not put any restriction on using classes as property values, in OWL DL and OWL Lite most properties cannot have classes as their values. We illustrate the direct approach for representing classes as property values in OWL-Full and RDF Schema. We present various alternative mechanisms for representing the required information in OWL DL and OWL Lite. For each approach, we discuss various considerations that the users should keep in mind when choosing the best approach for their purposes.
Editors
Natasha Noy.
Semantic Web Best Practices and Deployment Working Group- Family:
- RDF
The Resource Description Framework (RDF) is a framework for representing information in the Web.
RDF Concepts and Abstract Syntax defines an abstract syntax on which RDF is based, and which serves to link its concrete syntax to its formal semantics. It also includes discussion of design goals, key concepts, datatyping, character normalization and handling of URI references.
Editors
Graham Klyne, Jeremy Carroll.
RDF Core Working Group- Family:
- RDF
The Resource Description Framework (RDF) is a language for representing information about resources in the World Wide Web. This Primer is designed to provide the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and describes its XML syntax. It describes how to define RDF vocabularies using the RDF Vocabulary Description Language, and gives an overview of some deployed RDF applications. It also describes the content and purpose of other RDF specification documents.
Editors
Frank Manola, Eric Miller.
RDF Core Working Group- Family:
- RDF
This document describes the RDF Test Cases deliverable for the RDF Core Working Group as defined in the Working Group's Charter.
Editors
jan grant, Dave Beckett.
RDF Core Working Group- Family:
- RDF
This is a specification of a precise semantics, and corresponding complete systems of inference rules, for the Resource Description Framework (RDF) and RDF Schema (RDFS).
Editors
Patrick Hayes.
RDF Core Working Group- Family:
- RDF
CSS Font Loading
In progress
The CSS Font Loading module describes events and interfaces used for dynamically loading font resources.
Editors
Tab Atkins Jr..
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Font Loading
EmotionML
Complete
As the Web is becoming ubiquitous, interactive, and multimodal, technology needs to deal increasingly with human factors, including emotions. EmotionML provides mechanisms to represent emotions in terms of scientifically valid descriptors: categories, dimensions, appraisals, and action tendencies. It is conceived as a "plug-in" language suitable for use in three different areas: (1) manual annotation of data; (2) automatic recognition of emotion-related states from user behavior; and (3) generation of emotion-related system behavior.
Editors
Felix Burkhardt, Marc Schröder.
Multimodal Interaction Working Group- Family:
- EmotionML
This document represents a public collection of emotion vocabularies that can be used with EmotionML. It was originally part of an earlier draft of the EmotionML specification, but was moved out of it so that we can easily update, extend and correct the list of vocabularies as required.
Editors
Felix Burkhardt, Marc Schröder, Catherine Pelachaud.
Multimodal Interaction Working Group- Family:
- EmotionML
RDF Vocabulary
Complete
The document describes a mapping of the vCard specification (RFC6350) to RDF/OWL. The goal is to promote the use of vCard for the description of people and organisations utilising semantic web techniques and allowing compatibility with traditional vCard implementations.
Editors
Renato Iannella, James McKinney.
Semantic Web Interest Group- Family:
- RDF Vocabulary
This document describes a core ontology for organizational structures, aimed at supporting linked-data publishing of organizational information across a number of domains. It is designed to allow domain-specific extensions to add classification of organzations and roles, as well as extensions to support neighbouring information such as organizational activities.
Editors
Dave Reynolds.
Government Linked Data Working Group- Family:
- RDF Vocabulary
There are many situations where it would be useful to be able to publish multi-dimensional data, such as statistics, on the web in such a way that it can be linked to related data sets and concepts. The Data Cube vocabulary provides a means to do this using the W3C RDF (Resource Description Framework) standard.
Editors
Richard Cyganiak, Dave Reynolds.
Government Linked Data Working Group- Family:
- RDF Vocabulary
Available in:
日本語Many organizations collect and aggregate numeric data into statistics. In this document, the W3C Government Linked Data Working Group presents use cases and lessons supporting a recommendation of the RDF Data Cube Vocabulary. We describe case studies of existing deployments of an earlier version of the Data Cube Vocabulary as well as other possible use cases that would benefit from using the vocabulary.
Editors
Benedikt Kaempgen, Richard Cyganiak.
Government Linked Data Working Group- Family:
- RDF Vocabulary
This is a vocabulary for describing organizations that have gained legal entity status through a formal registration process, typically in a national or regional register. This document is the normative companion to the namespace document at http://www.w3.org/ns/regorg.
Editors
Phil Archer, Marios Meimaris, Agis Papantoniou.
Government Linked Data Working Group- Family:
- RDF Vocabulary
Editors
Dan Connolly, Libby Miller.
Semantic Web Interest Group- Family:
- RDF Vocabulary
In progress
This document defines a set of terms for describing people. It defines how to describe people's characteristics such as names or addresses and how to relate people to other things, for example to organizations or projects. For each term, guidance on the usage within a running example is provided. This document also defines mappings to widely used vocabularies to enable interoperability.
Editors
Michael Hausenblas.
Government Linked Data Working Group- Family:
- RDF Vocabulary
CSS Generated Content for Paged Media
In progress
This module describes features often used in printed publications. In particular, this specification describes how CSS style sheets can express running headers and footers, leaders, cross-references, footnotes, sidenotes, named flows, hyphenation, new counter styles, character substitution, image resolution, page floats, advanced multi-column layout, conditional content, crop and cross marks, bookmarks, CMYK colors, continuation markers, change bars, line numbers, named page lists, and generated lists. Along with two other CSS3 modules – multi-column layout and paged media – this module offers advanced functionality for presenting structured documents on paged media.
Editors
Dave Cramer.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Generated Content for Paged Media
XML
Complete
This document defines several sets of names which are assigned to Unicode characters. Each of these sets is also implemented as a file of XML entity declarations.
Editors
David Carlisle, Patrick D F Ion.
Math Working Group- Family:
- XML
Editors
Paul Grosso, Jirka Kosek.
XML Core Working Group- Family:
- XML
This document allows a style sheet to be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog.
Editors
James Clark, Simon Pieters, Henry Thompson.
XML Core Working Group- Family:
- XML
Available in:
русскийXML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references.
Editors
Tim Bray, Dave Hollander, Andrew Layman, Richard Tobin, Henry Thompson.
XML Core Working Group- Family:
- XML
This document describes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents.
Editors
Jonathan Marsh, Richard Tobin.
XML Core Working Group- Family:
- XML
The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.
Editors
Tim Bray, Jean Paoli, Michael Sperberg-McQueen, Eve Maler, François Yergeau.
XML Core Working Group- Family:
- XML
For historic reasons, some formats have allowed variants of IRIs that are somewhat less restricted in syntax, for example XML system identifiers and W3C XML Schema anyURIs. This document provides a definition and a name (Legacy Extended IRI or LEIRI) for these variants for easy reference.
Editors
Henry Thompson, Richard Tobin, Norman Walsh.
XML Core Working Group- Family:
- XML
Available in:
françaisThe Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML.
Editors
Tim Bray, Jean Paoli, Michael Sperberg-McQueen, Eve Maler, François Yergeau, John Cowan.
XML Core Working Group- Family:
- XML
XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by IRI references.
Editors
Tim Bray, Dave Hollander, Andrew Layman, Richard Tobin.
XML Core Working Group- Family:
- XML
This document defines the meaning of the attribute xml:id as an ID attribute in XML documents and defines processing of this attribute to identify IDs in the absence of validation, without fetching external resources, and without relying on an internal subset.
Editors
Jonathan Marsh, Daniel Veillard, Norman Walsh.
XML Core Working Group- Family:
- XML
This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document.
Editors
John Cowan, Richard Tobin.
XML Core Working Group- Family:
- XML
This W3C Note defines an RDF schema for the XML Infoset.
Editors
Richard Tobin.
XML Core Working GroupUNKNOWN WORKING GROUP
- Family:
- XML
This document is a report of the results of a meeting of a group of W3C Members involved in XML and RDF to advance the general understanding of a unified approach to the expression of Web data models. This document is one response to the Web data architecture discussed in "Web Architecture: Describing and Exchanging Data".
Editors
Henry Thompson.
UNKNOWN WORKING GROUP- Family:
- XML
Editors
Paul Grosso.
UNKNOWN WORKING GROUP- Family:
- XML
MathML
Complete
This specification defines the Mathematical Markup Language, or MathML. MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text.
Editors
David Carlisle, Patrick D F Ion, Robert R Miner.
Math Working Group- Family:
- MathML
This document describes a profile of MathML 3.0 that admits formatting with Cascading Style Sheets.
Editors
Bert Bos, David Carlisle, Giorgi Chavchanidze, Patrick D F Ion, Bruce Miller.
Math Working Group- Family:
- MathML
Available in:
日本語Analyzes potential problems with the use of MathML for the presentation of mathematics in the notations customarily used with Arabic, and related languages.
Editors
Azzeddine Lazrek, Bruce Miller.
Math Working Group- Family:
- MathML
This Note discusses the facilities that are available in the MathML 2.0 Recommendation to facilitate the capturing of mathematical type information. It demonstrates how a combination of these features can be systematically used to provide support for general mathematical types.
Editors
Stan Devitt, Michael Kohlhase, Max Froumentin.
Math Working Group- Family:
- MathML
MathML is an XML application for describing mathematical notation, capturing both its structure and content. As such, its scope does not extend to include units - determinate quantities adopted as standards of measure - which nevertheless, by their very nature, occur in an applied mathematical setting. This Note makes recommendations and suggestions for how units can be incorporated into MathML.
Editors
Douglas Harder, Stan Devitt.
Math Working Group- Family:
- MathML
Available in:
日本語This Note examines the treatment of bound variables in Content MathML. Bound variables are central representational primitives in mathematical languages. They allow one to express functions, quantification, and operators with qualifiers. The first edition of the MathML 2.0 Recommendation [MathML2] was somewhat vague about the identity conditions on bound variables, and as a consequence Content MathML applications were left to guess the exact meaning. This Note provides some of the rationale behind how this has been clarified in the second edition [MathML22e].
Editors
Stan Devitt, Michael Kohlhase.
Math Working Group- Family:
- MathML
This specification defines the Mathematical Markup Language, or MathML. MathML is an XML application for describing mathematical notation and capturing both its structure and content. The goal of MathML is to enable mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for text.
This specification of the markup language MathML is intended primarily for a readership consisting of those who will be developing or implementing renderers or editors using it, or software that will communicate using MathML as a protocol for input or output. It is not a User's Guide but rather a reference document.
This document begins with background information on mathematical notation, the problems it poses, and the philosophy underlying the solutions MathML 2.0 proposes. MathML can be used to encode both mathematical notation and mathematical content. About thirty of the MathML tags describe abstract notational structures, while another about one hundred and fifty provide a way of unambiguously specifying the intended meaning of an expression. Additional chapters discuss how the MathML content and presentation elements interact, and how MathML renderers might be implemented and should interact with browsers. Finally, this document addresses the issue of MathML characters and their relation to fonts.
While MathML is human-readable, it is anticipated that, in all but the simplest cases, authors will use equation editors, conversion programs, and other specialized software tools to generate MathML. Several versions of such MathML tools already exist, and a number of others, both freely available software and commercial products, are under development.
Editors
David Carlisle, Patrick D F Ion, Robert R Miner, Nico Poppelier.
Math Working Group- Family:
- MathML
Editors
Patrick D F Ion, Robert R Miner.
Math Working Group- Family:
- MathML
CSS Scoping
In progress
This specification defines various scoping/encapsulation mechanisms for CSS, including scoped styles and the @scope rule, Shadow DOM selectors, and page/region-based styling.
Editors
Tab Atkins Jr., Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Scoping
Device API
Complete
This document reviews of the usage of type of network connectivity in existing mobile applications to determine what use cases a network information API would need to enable.
Editors
Marcos Caceres, Fernando Jiménez Moreno, Ernesto Jimenez.
Web and Mobile Interest Group- Family:
- Device API
Editors
Giuseppe Pascale.
Devices and Sensors Working GroupMedia and Entertainment Interest Group
- Family:
- Device API
This document defines requirements for controlling access to device APIs, illustrated by corresponding use cases.
Editors
Laura Arribas, Frederick Hirsch, Dominique Hazaël-Massieux.
Devices and Sensors Working Group- Family:
- Device API
This document provides definitions, use cases, and requirements for making device APIs more privacy-friendly.
Editors
Alissa Cooper, Frederick Hirsch, John Morris.
Devices and Sensors Working Group- Family:
- Device API
These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.
Editors
Robin Berjon, Daniel Coloma, Max Froumentin, Marcin Hanclik, Jere Käpyaho, Kangchan Lee, Bryan Sullivan, Dzung Tran.
Devices and Sensors Working Group- Family:
- Device API
CSS Shapes
In progress
CSS Shapes control the geometric shapes used for wrapping inline flow content outside an element.
Editors
Vincent Hardy, Rossen Atanassov, Alan Stearns.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Shapes
CSS Namespaces
Complete
This CSS Namespaces module defines the syntax for using namespaces in CSS. It defines the @namespace rule for declaring the default namespace and binding namespaces to namespace prefixes, and it also defines a syntax that other specifications can adopt for using those prefixes in namespace-qualified names.
Editors
Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Namespaces
Media Resources
Complete
This specification defines a client-side API to access metadata information related to media resources on the Web.
Editors
Florian Stegmaier, Werner Bailer, Martin Höffernig, Wonsuk Lee, Chris Poppe.
Media Annotations Working Group- Family:
- Media Resources
Available in:
日本語This document defines the Ontology for Media Resources 1.0. The term "Ontology" is used in its broadest possible definition: a core vocabulary. The intent of this vocabulary is to bridge the different descriptions of media resources, and provide a core set of descriptive properties. This document defines a core set of metadata properties for media resources, along with their mappings to elements from a set of existing metadata formats. Besides that, the document presents a Semantic Web compatible implementation of the abstract ontology using RDF/OWL. The document is mostly targeted towards media resources available on the Web, as opposed to media resources that are only accessible in local repositories.
Editors
Wonsuk Lee, Werner Bailer, Tobias Bürger, Pierre-Antoine Champin, Jean-Pierre EVAIN, Véronique Malaisé, Thierry Michel, Felix Sasaki, Joakim Söderberg, Florian Stegmaier, John Strassner.
Media Annotations Working Group- Family:
- Media Resources
Available in:
日本語In progress
Add content here.
Editors
Wonsuk Lee, Tobias Bürger, Felix Sasaki, Véronique Malaisé.
Media Annotations Working Group- Family:
- Media Resources
Best Practices for Publishing Linked Data
Complete
A compilation of Best Practices for publishing data as Linked Data, for when organizations want their data available for use by others. Written with a focus on Government data, but also useful for scientific, commercial, and other open data needs.
Editors
Bernadette Hyland, Ghislain Auguste Atemezing, Boris Villazón-Terrazas.
Government Linked Data Working Group- Family:
- Best Practices for Publishing Linked Data
MBUI
Complete
This document is a glossary of terms recurrent in the Model-based User Interface domain (MBUI). It is intended to capture a common, coherent terminology for specifications of the MBUI Working Group and to provide a concise reference of domain terms for interested audience. The document arose from a thorough review and discussion of the glossaries published by the CAMELEON and AMODEUS research projects.
Editors
Jaroslav Pullmann.
Model-Based User Interfaces Working Group- Family:
- MBUI
This is an introduction to Model-Based User Interfaces covering the benefits and shortcomings of the model-based approach, a collection of use cases, and terminology.
Editors
Gerrit Meixner, Gaelle Calvary.
Model-Based User Interfaces Working Group- Family:
- MBUI
CSS Style Attributes
Complete
Describes the syntax and interpretation of the CSS fragment that can be used in "style" attributes inside mark-up, e.g., in HTML, SVG and MathML.
Editors
Tantek Çelik, Elika Etemad.
Cascading Style Sheets (CSS) Working Group- Family:
- CSS Style Attributes
ITS
Complete
This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS) 2.0. ITS 2.0 is the successor of ITS 1.0; it is designed to foster the creation of multilingual Web content, focusing on HTML5, XML based formats in general, and to leverage localization workflows based on the XML Localization Interchange File Format (XLIFF). In addition to HTML5 and XML, algorithms to convert ITS attributes to RDFa and NIF are provided.
Editors
David Filip, Shaun McCance, David Lewis, Christian Lieske, Arle Lommel, Jirka Kosek, Felix Sasaki, Yves Savourel.
MultilingualWeb-LT Working Group- Family:
- ITS
Available in:
日本語This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS). ITS is designed to be used with schemas to support the internationalization and localization of schemas and documents. An implementation is provided for three schema languages: XML DTD, XML Schema and RELAX NG.
Editors
Christian Lieske, Felix Sasaki.
Internationalization Tag Set (ITS) Working Group- Family:
- ITS
Available in:
françaisTouch Events
Complete
This specification defines low-level events representing points of contact with a touch-sensitive surface.
Editors
Doug Schepers, Sangwhan Moon, Matt Brubeck, Arthur Barstow.
Web Events Working Group- Family:
- Touch Events
EMMA
Complete
Editors
Michael Johnston.
Multimodal Interaction Working Group- Family:
- EMMA
The W3C Multimodal Interaction Working Group aims to develop specifications to enable access to the Web using multimodal interaction. This document is part of a set of specifications for multimodal systems, and provides details of an XML markup language for containing and annotating the interpretation of user input. Examples of interpretation of user input are a transcription into words of a raw signal, for instance derived from speech, pen or keystroke input, a set of attribute/value pairs describing their meaning, or a set of attribute/value pairs describing a gesture. The interpretation of the user's input is expected to be generated by signal interpretation processes, such as speech and ink recognition, semantic interpreters, and other types of processors for use by components that act on the user's inputs such as interaction managers.
Editors
Michael Johnston.
Multimodal Interaction Working Group- Family:
- EMMA
This document describes requirements for the Extensible MultiModal Annotation language (EMMA) specification under development in the W3C Multimodal Interaction Activity. EMMA is intended as a data format for the interface between input processors and interaction management systems. It will define the means for recognizers to annotate application specific data with information such as confidence scores, time stamps, input mode (e.g. key strokes, speech or pen), alternative recognition hypotheses, and partial recognition results, etc. EMMA is a target data format for the semantic interpretation specification being developed in the Voice Browser Activity, and which describes annotations to speech grammars for extracting application specific data as a result of speech recognition. EMMA supercedes earlier work on the natural language semantics markup language in the Voice Browser Activity.
Editors
Stéphane Maes, Stephen Potter.
Multimodal Interaction Working Group- Family:
- EMMA
In progress
EMMA is an XML markup language for containing and annotating the interpretation of user input like a transcription into words of a raw signal, for instance derived from speech, pen or keystroke input. EMMA 1.0 was published as a W3C Recommendation in February 2009. Since then there have been numerous implementations of the standard and extensive feedback has come in regarding desired new features and clarifications needed of existing features. The Multimodal Interaction Working Group examined a range of different use cases for extensions and published a W3C Note on Use Cases for Possible Future EMMA Features. This Version 1.1 document describes a set of new features based on feedback from implementers.
Editors
Michael Johnston.
Multimodal Interaction Working Group- Family:
- EMMA
XML Canonicalization
Complete
This document outlines test cases for Canonical XML 2.0, a major revision of XML canonicalization. It currently includes tests from Canonical XML 1.0 and new tests related to XML namespace handling.
Editors
Pratik Datta, Frederick Hirsch.
XML Security Working Group- Family:
- XML Canonicalization
Canonicalization 2.0 dovetails with the XML Signature 2.0 specification, and provides an XML canonicalization mechanism that is optimized for the needs of that specification.
Editors
John Boyer, Glenn Marcy, Pratik Datta, Frederick Hirsch.
XML Security Working Group- Family:
- XML Canonicalization
Canonical XML Version 1.1 is a revision to Canonical XML Version 1.0 to address issues related to inheritance of attributes in the XML namespace when canonicalizing document subsets, including the requirement not to inherit xml:id, and to treat xml:base URI path processing properly.
Any XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 [XML] and Namespaces in XML 1.0 [Names]. This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account.
Canonical XML Version 1.1 is applicable to XML 1.0 and defined in terms of the XPath 1.0 data model. It is not defined for XML 1.1.
Editors
John Boyer, Glenn Marcy.
XML Core Working Group- Family:
- XML Canonicalization
This technical note addresses some of the issues related to inheritance of the XML attributes xml:base and xml:id and the W3C Recommendation for Canonical XML Version 1.0 [C14N10] (Errata). Shortcomings of C14N/1.0 are noted out and the use of a new C14N/1.1 recommendation with the XML Digital Signature 1.0 Recommendation [XMLDSIG] is discussed.
Editors
José Kahan, Konrad Lanz.
XML Core Working Group- Family:
- XML Canonicalization
Canonical XML [XML-C14N] specifies a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and attributes in the "xml:" namespace. However, some applications require a method which, to the extent practical, excludes ancestor context from a canonicalized subdocument. For example, one might require a digital signature over an XML payload (subdocument) in an XML message that will not break when that subdocument is removed from its original message and/or inserted into a different context. This requirement is satisfied by Exclusive XML Canonicalization.
Editors
John Boyer, Donald Eastlake, Joseph Reagle.
XML Security Working Group- Family:
- XML Canonicalization
Available in:
françaisAny XML document is part of a set of XML documents that are logically equivalent within an application context, but which vary in physical representation based on syntactic changes permitted by XML 1.0 [XML] and Namespaces in XML [Names]. This specification describes a method for generating a physical representation, the canonical form, of an XML document that accounts for the permissible changes. Except for limitations regarding a few unusual cases, if two documents have the same canonical form, then the two documents are logically equivalent within the given application context. Note that two documents may have differing canonical forms yet still be equivalent in a given context based on application-specific equivalence rules for which no generalized XML specification could account.
Editors
John Boyer.
XML Security Working GroupUNKNOWN WORKING GROUP
- Family:
- XML Canonicalization
Editors
James Tauber, Joel Nava.
UNKNOWN WORKING GROUP- Family:
- XML Canonicalization
PROV
Complete
Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. This document describes extensions to PROV to facilitate the modeling of provenance for dictionary data structures. [PROV-DM] specifies a Collection as an entity that provides a structure to some constituents, which are themselves entities. However, some applications may need a mechanism to specify more structure to a Collection, in order to accurately describe its provenance. Therefore, in this document, we introduce Dictionary, a specific type of Collection with a logical structure consisting of key-value pairs.
The PROV Document Overview describes the overall state of PROV, and should be read before other PROV documents.
Editors
Tom De Nies, Sam Coppens.
Provenance Working Group- Family:
- PROV
This specification defines the PROV Ontology as the normative representation of the PROV Data Model using the Web Ontology Language (OWL2). This document is part of a set of specifications being created to address the issue of provenance interchange in Web applications.
Editors
Timothy Lebo, Satya Sahoo, Deborah McGuinness.
Provenance Working Group- Family:
- PROV
Available in:
日本語PROV-DM is a core data model for provenance for building representations of the entities, people and processes involved in producing a piece of data or thing in the world. PROV-DM is domain-agnotisc, but with well-defined extensibility points allowing further domain-specific and application-specific extensions to be defined. It is accompanied by PROV-ASN, a technology-independent abstract syntax notation, which allows serializations of PROV-DM instances to be created for human consumption, which facilitates its mapping to concrete syntax, and which is used as the basis for a formal semantics.
Editors
Luc Moreau, Paolo Missier.
Provenance Working Group- Family:
- PROV
Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The PROV Family of Documents defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web. This document provides an overview this family of documents.
Editors
Paul Groth, Luc Moreau.
Provenance Working Group- Family:
- PROV
This document reports on implementations and usage of the four normative specifications ([PROV-DM], [PROV-N], [PROV-O], [PROV-CONSTRAINTS]) of the PROV Family of Documents [PROV-OVERVIEW]. In particular, it's aim is to demonstrate that the features defined in PROV are implementable and interoperable. Features are defined as: the constructs specified in [PROV-DM] and their realisation in OWL (see [PROV-O]) and in the [PROV-N] syntax; the constraints defined within [PROV-CONSTRAINTS]. Interoperability is defined through both the interchange of provenance information and the coverage of test cases.
Editors
Trung Dong Huynh, Paul Groth, Stephan Zednik.
Provenance Working Group- Family:
- PROV
This document provides an intuitive introduction and guide to the PROV data model for provenance (PROV-DM). This primer explains the fundamental PROV-DM concepts in non-normative terms, and provides worked examples applying the PROV-O OWL2 ontology, and is intended as a starting point for those wishing to create or make use of PROV-DM data.
Editors
Yolanda Gil, Simon Miles.
Provenance Working Group- Family:
- PROV
Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. Bundles, defined in as sets of provenance descriptions, were introduced in PROV as the mechanism by which provenance of provenance can be expressed. Bundles, whose validity is established independently of each other [PROV-CONSTRAINTS], are essentially independent of each other, acting as islands of provenance descriptions.
Editors
Luc Moreau, Timothy Lebo.
Provenance Working Group- Family:
- PROV
This document presents a model-theoretic semantics for the PROV data model (called the naive semantics), viewing PROV-DM statements as atomic formulas in the sense of first-order logic, and viewing the constraints and inferences specified in PROV-CONSTRAINTS as a first-order theory. It is shown that the first-order theory is sound with respect to the naive semantics. This information may be useful to researchers or users of PROV to understand the intended meaning and use of PROV for modeling information about the actual history, derivation or evolution of Web resources. It may also be useful for development of additional constraints or inferences for reasoning about PROV or integration of PROV with other Semantic Web vocabularies. It is not proposed as a canonical or required semantics of PROV and does not place any constraints on the use of PROV.
Editors
James Cheney.
Provenance Working Group- Family:
- PROV
This document specifies how to use standard Web protocols, including HTTP, to obtain information about the provenance of Web resources.
Editors
Graham Klyne, Paul Groth.
Provenance Working Group- Family:
- PROV
PROV-DM, the PROV data model, is a data model for provenance that describes the entities, people and activities involved in producing a piece of data or thing. PROV-DM is structured in six components, dealing with: (1) entities and activities, and the time at which they were created, used, or ended; (2) agents bearing responsibility for entities that were generated and activities that happened; (3) derivations of entities from entities; (4) properties to link entities that refer to the same thing; (5) collections forming a logical structure for its members; (6) a simple annotation mechanism.
To provide examples of the PROV data model, the PROV notation (PROV-N) is introduced: aimed at human consumption, PROV-N allows serializations of PROV instances to be created in a compact manner. PROV-N facilitates the mapping of the PROV data model to concrete syntax, and is used as the basis for a formal semantics of PROV. The purpose of this document is to define the PROV-N notation.
Editors
Luc Moreau, Paolo Missier.
Provenance Working Group- Family:
- PROV
Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. PROV-DM is the conceptual data model that forms a basis for the W3C provenance (PROV) family of specifications. It defines a concepts for expressing provenance information enabling interchange. This document introduces an XML schema for the PROV data model (PROV-DM), allowing instances of the PROV data model to be serialized in XML.
Editors
Hook Hua, Curt Tilmes, Stephan Zednik.
Provenance Working Group- Family:
- PROV
PROV-DM, the PROV data model, is a data model for provenance that describes the entities, people and activities involved in producing a piece of data or thing. PROV-DM is structured in six components, dealing with: (1) entities and activities, and the time at which they were created, used, or ended; (2) agents bearing responsibility for entities that were generated and activities that happened; (3) derivations of entities from entities; (4) properties to link entities that refer to a same thing; (5) collections forming a logical structure for its members; (6) a simple annotation mechanism.
This document introduces a further set of concepts useful for understanding the PROV data model and defines inferences that are allowed on provenance statements and validity constraints that PROV instances should follow. These inferences and constraints are useful for readers who develop applications that generate provenance or reason over provenance.
Editors
James Cheney, Paolo Missier, Luc Moreau.
Provenance Working Group- Family:
- PROV
This document provides a mapping between the PROV-O OWL2 ontology and the Dublin Core Terms Vocabulary.
Editors
Daniel Garijo, Kai Eckert.
Provenance Working Group- Family:
- PROV
XML Encryption
Complete
Generic hybrid ciphers allow for a consistent treatment of asymmetric ciphers when encrypting data and consist of a key encapsulation algorithm with associated parameters and a data encapsulation algorithm with associated parameters. This document augments XML Encryption Version 1.1 by defining algorithms, XML types and elements necessary to enable use of generic hybrid ciphers in XML Security applications.
Editors
Magnus Nyström, Frederick Hirsch.
XML Security Working Group- Family:
- XML Encryption
This document specifies how the XML Signature 2.0 transform model may be used with XML Encryption 1.1 for CipherReference processing.
Editors
Frederick Hirsch.
XML Security Working Group- Family:
- XML Encryption
Add content here.
Editors
Frederick Hirsch, Thomas Roessler, Kelvin Yiu.
XML Security Working Group- Family:
- XML Encryption
Add content here.
Editors
Donald Eastlake, Joseph Reagle, Frederick Hirsch, Thomas Roessler.
XML Security Working Group- Family:
- XML Encryption
Editors
Frederick Hirsch.
XML Security Working Group- Family:
- XML Encryption
Editors
Pratik Datta, Frederick Hirsch.
XML Security Working Group- Family:
- XML Encryption
This document lists the design principles, scope, and requirements for XML Encryption. It includes requirements as they relate to the encryption syntax, data model, format, cryptographic processing, and external requirements and coordination.
Editors
Joseph Reagle.
XML Security Working Group- Family:
- XML Encryption
SPARQL
Complete
The goal of this document is to specify conditions such that SPARQL can be used with entailment regimes other than simple entailment. Currently the semantics of SPARQL queries under RDF and RDFS entailment is defined. Time permitting, entailment regimes will also be defined for D-entailment, OWL with Direct and RDF-Based semantics including OWL 2 Profiles, and the rule interchange format RIF.
Editors
Birte Glimm, Chimezie Ogbuji.
SPARQL Working Group- Family:
- SPARQL
Available in:
ΕλληνικάThe SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it uses WSDL 2.0 to describe a means for conveying SPARQL queries to an SPARQL query processing service and returning the query results to the entity that requested them.
Editors
Lee Feigenbaum, Gregory Williams, Kendall Clark, Elias Torres.
SPARQL Working Group- Family:
- SPARQL
RDF is a flexible, extensible way to represent information about World Wide Web resources. It is used to represent, among other things, personal information, social networks, metadata about digital artifacts like music and images, as well as provide a means of integration over disparate sources of information. A standardized query language for RDF data with multiple implementations offers developers and end users a way to write and to consume the results of queries across this wide range of information.
This document describes an XML format for the variable binding and boolean results formats provided by the SPARQL query language for RDF, developed by the W3C RDF Data Access Working Group (DAWG), part of the Semantic Web Activity as described in the activity statement .
Editors
Dave Beckett, Jeen Broekstra.
SPARQL Working Group- Family:
- SPARQL
This specification defines the syntax and semantics of SPARQL 1.1 Federated Query extension for executing queries ../distributed over different SPARQL endpoints.
Editors
Eric Prud'hommeaux, Carlos Buil Aranda.
SPARQL Working Group- Family:
- SPARQL
RDF is a directed, labeled graph data format for representing information in the Web. The SPARQL specification defines the syntax and semantics of the SPARQL query language for RDF. This document describes changes that will be made to the SPARQL query language to form SPARQL 1.1 Query.
Editors
Steven Harris, Andy Seaborne.
SPARQL Working Group- Family:
- SPARQL
SPARQL provides a standard way to query RDF data. The SPARQL update language allows a user to update RDF graphs in an RDF dataset at various levels of granularity, including individual RDF statements. The protocol described here is meant to provide a minimal set of uniform, colloquial HTTP operations for managing a semantic web of network-manipulable RDF at a strictly large level of granularity.
Editors
Chimezie Ogbuji.
SPARQL Working Group- Family:
- SPARQL
Available in:
ΕλληνικάThe formats CSV [RFC4180] (comma separated values) and TSV [IANA-TSV] (tab separated values) provide simple, easy to process formats for the transmission of tabular data. They are supported as input datat formats to many tools, particularly spreadsheets. This document describes their use for expressing SPARQL query results from SELECT queries.
Editors
Andy Seaborne.
SPARQL Working Group- Family:
- SPARQL
This document is an overview of SPARQL 1.1. It provides an introduction to a set of W3C specifications that facilitate querying and manipulating RDF graph content on the Web or in an RDF store.
SPARQL Working Group- Family:
- SPARQL
This document describes the representation of SELECT and ASK query results using JSON.
Editors
Andy Seaborne.
SPARQL Working Group- Family:
- SPARQL
This document describes SPARQL Service Descriptions, a method for discovering and vocabulary for describing SPARQL services made available via the SPARQL Protocol. Such descriptions are intended to provide a mechanism by which a client or end user can discover information about the SPARQL implementation/service such as supported extension functions and details about the available dataset.
Editors
Gregory Williams.
SPARQL Working Group- Family:
- SPARQL
This document describes SPARQL-Update, an update language for RDF graphs. It uses a syntax derived from SPARQL. Update operations are performed on a collection of graphs in a Graph Store. Operations are provided to change existing RDF graphs as well as create and remove graphs in the Graph Store.
Editors
Paula Gearon, Alexandre Passant, Axel Polleres.
SPARQL Working Group- Family:
- SPARQL
RDF is a directed, labeled graph data format for representing information in the Web. This specification defines the syntax and semantics of the SPARQL query language for RDF. SPARQL can be used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. SPARQL contains capabilities for querying required and optional graph patterns along with their conjunctions and disjunctions. SPARQL also supports extensible value testing and constraining queries by source RDF graph. The results of SPARQL queries can be results sets or RDF graphs.
Editors
Eric Prud'hommeaux, Andy Seaborne.
SPARQL Working Group- Family:
- SPARQL
The SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it uses WSDL 2.0 to describe a means for conveying SPARQL queries to an SPARQL query processing service and returning the query results to the entity that requested them. This protocol was developed by the W3C RDF Data Access Working Group (DAWG), part of the Semantic Web Activity as described in the activity statement .
Editors
Kendall Clark, Lee Feigenbaum, Elias Torres.
SPARQL Working Group- Family:
- SPARQL
This document describes an JSON format for the variable binding and boolean results formats provided by the SPARQL query language for RDF.
Editors
Kendall Clark, Lee Feigenbaum, Elias Torres.
SPARQL Working Group- Family:
- SPARQL
In progress
SPARQL is a query language for RDF data on the Semantic Web with formally defined meaning. This document is a simple introduction to the new features of the language, including an explanation of its differences with respect to the previous SPARQL Query Language Recommendation [SPARQL/Query 1.0]. It also presents the requirements that have motivated the design of the main new features, and their rationale from a theoretical and implementation perspective.
Editors
Kjetil Kjernsmo, Alexandre Passant.
SPARQL Working Group- Family:
- SPARQL
RIF
Complete
A RIF dialect building on RIF Core by adding function terms (Horn logic) and equality in the rule conclusions.
Editors
Harold Boley, Michael Kifer.
Rule Interchange Format Working Group- Family:
- RIF
A RIF dialect for expressing the kind of rules used by production rule engines, such as commonly found in Business Rule systems
Editors
Christian de Sainte Marie, Gary Hallmark, Adrian Paschke.
Rule Interchange Format Working Group- Family:
- RIF
The minimum RIF dialect (datalog with builtins), to which other RIF dialects add extensions.
Editors
Harold Boley, Gary Hallmark, Michael Kifer, Adrian Paschke, Axel Polleres, Dave Reynolds.
Rule Interchange Format Working Group- Family:
- RIF
Editors
Leora Morgenstern, Christopher Welty, Harold Boley, Gary Hallmark.
Rule Interchange Format Working Group- Family:
- RIF
The list of datatypes, built-in functions, and built-in predicates supported by all RIF dialects, based on XML Schema, XML Query, and XPath.
Editors
Axel Polleres, Harold Boley, Michael Kifer.
Rule Interchange Format Working Group- Family:
- RIF
A formal specification for how RIF can be used with RDF and OWL, including the semantics of different ways of importing RDF data and OWL ontologies into RIF rule systems.
Editors
Jos de Bruijn, Christopher Welty.
Rule Interchange Format Working Group- Family:
- RIF
Specifies a coherent way to build more-expressive RIF dialects, using a single semantic framework.
Editors
Harold Boley, Michael Kifer.
Rule Interchange Format Working Group- Family:
- RIF
Documentation for the RIF test suite and suggested RIF testing process.
Editors
Stella Mitchell, Leora Morgenstern, Adrian Paschke.
Rule Interchange Format Working Group- Family:
- RIF
Specifies a way to encode RIF documents in RDF, allowing rules to be stored and processed as RDF triples; can also be used for writing RIF rules which transform RIF rules.
Editors
Sandro Hawke, Axel Polleres.
Rule Interchange Format Working Group- Family:
- RIF
An enumeration of the main use cases considered by the RIF Working Group, and design requirements than emerged from those use cases and guided the overall design of RIF.
Editors
Adrian Paschke, Leora Morgenstern, David Hirtle, Allen Ginsberg, Paula-Lavinia Patranjan, Francis McCabe.
Rule Interchange Format Working Group- Family:
- RIF
An overview of the Rule Interchange Format (RIF), including a high-level explanation of RIF concepts and architecture and a survey of other RIF documents.
Editors
Michael Kifer, Harold Boley.
Rule Interchange Format Working Group- Family:
- RIF
Specification for how RIF rules can operate on XML data.
Editors
Christian de Sainte Marie.
Rule Interchange Format Working Group- Family:
- RIF
OWL
Complete
A detailed explanation of how to implement OWL 2 RL reasoning using RIF Core.
Editors
Dave Reynolds.
Rule Interchange Format Working Group- Family:
- OWL
Editors
Peter Patel-Schneider, Boris Motik.
OWL Working Group- Family:
- OWL
This document serves as an introduction to OWL 2 and the various other OWL 2 documents. It describes the syntaxes for OWL 2, the different kinds of semantics, the available profiles (sub-languages), and the relationship between OWL 1 and OWL 2.
OWL Working Group- Family:
- OWL
Available in:
日本語
Editors
Pascal Hitzler, Markus Krötzsch, Bijan Parsia, Peter Patel-Schneider, Sebastian Rudolph.
OWL Working Group- Family:
- OWL
This document provides the direct model-theoretic semantics for OWL 2, which is compatible with the description logic SROIQ. Furthermore, this document defines the most common inference problems for OWL 2.
Editors
Boris Motik, Peter Patel-Schneider, Bernardo Cuenca Grau.
OWL Working Group- Family:
- OWL
Editors
Boris Motik, Bernardo Cuenca Grau, Ian Horrocks, Zhe Wu, Achille Fokoue.
OWL Working Group- Family:
- OWL
Editors
Boris Motik, Peter Patel-Schneider, Bijan Parsia.
OWL Working Group- Family:
- OWL
This document describes the conditions that OWL 2 tools must satisfy in order to be conformant with the language specification. It also presents a common format for OWL 2 test cases that both illustrate the features of the language and can be used for testing conformance.
Editors
Michael[tm] Smith, Ian Horrocks, Markus Krötzsch, Birte Glimm.
OWL Working Group- Family:
- OWL
Add content here.
Editors
Jie Bao, Elisa Kendall, Deborah McGuinness, Peter Patel-Schneider.
OWL Working Group- Family:
- OWL
Editors
Bijan Parsia, Uli Sattler.
OWL Working Group- Family:
- OWL
Editors
Michael Schneider.
OWL Working Group- Family:
- OWL
Add content here.
Editors
Matthew Horridge, Peter Patel-Schneider.
OWL Working Group- Family:
- OWL
Editors
Boris Motik, Bijan Parsia, Peter Patel-Schneider.
OWL Working Group- Family:
- OWL
Add content here.
Editors
Christine Golbreich, Evan Wallace.
OWL Working Group- Family:
- OWL
Modelling various descriptive "features" (also known variously as "qualities", "attributes" or "modifiers") is a frequent requirement when creating ontologies. For example: "size" may describe persons or other physical objects and be constrained to take the values "small", "medium" or "large"; rank may describe military officers and restricted to a specific list of values depending on the military organisation. In OWL such descriptive features are modelled as properties whose range specifies the constraints on the values that the property can take on. This document describes two methods to represent such features and their specified values: 1) as partitions of classes; and 2) as enumerations of individuals. It does not discuss the use of datatypes to represent lists of values.
Editors
Alan Rector.
Semantic Web Best Practices and Deployment Working Group- Family:
- OWL
Editors
Peter Patel-Schneider, Patrick Hayes, Ian Horrocks.
Web Ontology Working Group- Family:
- OWL
The Web Ontology Language OWL is a semantic markup language for publishing and sharing ontologies on the World Wide Web. OWL is developed as a vocabulary extension of RDF (the Resource Description Framework) and is derived from the DAML+OIL Web Ontology Language. This document contains a structured informal description of the full set of OWL language constructs and is meant to serve as a reference for OWL users who want to construct OWL ontologies.
Editors
Mike Dean, Guus Schreiber.
Web Ontology Working Group- Family:
- OWL
This document contains and presents test cases for the Web Ontology Language (OWL) approved by the Web Ontology Working Group. Many of the test cases illustrate the correct usage of the Web Ontology Language (OWL), and the formal meaning of its constructs. Other test cases illustrate the resolution of issues considered by the Working Group. Conformance for OWL documents and OWL document checkers is specified.
Editors
Jeremy Carroll, Jos De Roo.
Web Ontology Working Group- Family:
- OWL
The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans. OWL facilitates greater machine interpretability of Web content than that supported by XML, RDF, and RDF Schema (RDF-S) by providing additional vocabulary along with a formal semantics. OWL has three increasingly-expressive sublanguages: OWL Lite, OWL DL, and OWL Full.
This document is written for readers who want a first impression of the capabilities of OWL. It provides an introduction to OWL by informally describing the features of each of the sublanguages of OWL. Some knowledge of RDF Schema is useful for understanding this document, but not essential. After this document, interested readers may turn to the OWL Guide for more detailed descriptions and extensive examples on the features of OWL. The normative formal definition of OWL can be found in the OWL Semantics and Abstract Syntax.
Editors
Deborah McGuinness, Frank van Harmelen.
Web Ontology Working Group- Family:
- OWL
This document specifies usage scenarios, goals and requirements for a web ontology language. An ontology formally defines a common set of terms that are used to describe and represent a domain. Ontologies can be used by automated tools to power advanced services such as more accurate web search, intelligent software agents and knowledge management.
Editors
Jeff Heflin.
Web Ontology Working Group- Family:
- OWL
The World Wide Web as it is currently constituted resembles a poorly mapped geography. Our insight into the documents and capabilities available are based on keyword searches, abetted by clever use of document connectivity and usage patterns. The sheer mass of this data is unmanageable without powerful tool support. In order to map this terrain more precisely, computational agents require machine-readable descriptions of the content and capabilities of Web accessible resources. These descriptions must be in addition to the human-readable versions of that information.
The OWL Web Ontology Language is intended to provide a language that can be used to describe the classes and relations between them that are inherent in Web documents and applications.
This document demonstrates the use of the OWL language to
- formalize a domain by defining classes and properties of those classes,
- define individuals and assert properties about them, and
- reason about these classes and individuals to the degree permitted by the formal semantics of the OWL language.
The sections are organized to present an incremental definition of a set of classes, properties and individuals, beginning with the fundamentals and proceeding to more complex language components.
Editors
Christopher Welty, Deborah McGuinness.
Web Ontology Working Group- Family:
- OWL
An OWL-RDF parser takes an RDF/XML file and attempts to construct an OWL ontology that corresponds to the triples represented in the RDF. This document describes a basic strategy that could be used in such a parser. Note that this is not intended as a complete specification, but hopefully provides enough information to point the way towards how one would build a parser that will deal with a majority of (valid) OWL ontologies.
For example, we do not discuss the implementation or handling of owl:imports here, nor do we address in depth issues concerned with spotting some of the more obscure violations of the DL/Lite rules.
Editors
Sean Bechhofer.
Web Ontology Working Group- Family:
- OWL
This document specifies XML presentation syntax for OWL, which is defined as a dialect similar to OWL Abstract Syntax [OWL Semantics]. It is not intended to be a normative specification. Instead, it represents a suggestion of one possible XML presentation syntax for OWL.
Editors
Masahiro Hori, Jérôme Euzenat, Peter Patel-Schneider.
Web Ontology Working Group- Family:
- OWL
MMI
Complete
This document describes a loosely coupled architecture for multimodal user interfaces, which allows for co-resident and ../distributed implementations, and focuses on the role of markup and scripting, and the use of well defined interfaces between its constituents.
Multimodal Interaction Working Group- Family:
- MMI
Editors
B Helena RODRIGUEZ.
Multimodal Interaction Working Group- Family:
- MMI
Editors
Ingmar Kliche.
Multimodal Interaction Working Group- Family:
- MMI
Editors
Ingmar Kliche.
Multimodal Interaction Working Group- Family:
- MMI
This document describes a multimodal system which implements the W3C Multimodal Architecture and gives an example of a simple multimodal application authored using various W3C markup languages, including SCXML, CCXML, VoiceXML 2.1 and HTML.
Editors
Ingmar Kliche.
Multimodal Interaction Working Group- Family:
- MMI
This document is based on the accumulated experience of several years of developing multimodal applications. It provides a collection of common sense advice for developers of multimodal user interfaces.
Editors
Jim Larson.
Multimodal Interaction Working Group- Family:
- MMI
Several years of multimodal application development in various business areas and on various device platforms has provided developers enough experience to provide detailed feedback about what they like, dislike, and want to see improve and continue. This experience is provided here as an input to the specifications under development in the W3C Multimodal Interaction and Voice Browser Activities.
Editors
Gerald McCobb, Klaus Reifenrath, Raj Tumuluri, Sunil Kumar.
Multimodal Interaction Working Group- Family:
- MMI
This document describes the DOM capabilities needed to support a heterogeneous multimodal environment and the current state of DOM interfaces supporting those capabilities. These DOM interfaces are used between modality components and their host environment in the W3C Multimodal Interaction Framework as proposed by the W3C Multimodal Interaction Activity.
The Multimodal Interaction Framework separates multimodal systems into a set of functional units, including Input and Output components, an Interaction Mananger, Session Components, System and Environment, and Application Functions. In order for those functional components to interact with each other to form an application interpreter, the browser implementation must allow for communication and coordination between those components. This DOM interface identifies the DOM APIs used to communicate and coordinate at the browser implemention level. Multimodal browsers can be stand-alone or ../distributed systems.
Editors
Brandon Porter.
Multimodal Interaction Working Group- Family:
- MMI
This document introduces the W3C Multimodal Interaction Framework, and identifies the major components for multimodal systems. Each component represents a set of related functions. The framework identifies the markup languages used to describe information required by components and for data flowing among components. The W3C Multimodal Interaction Framework describes input and output modes widely used today and can be extended to include additional modes of user input and output as they become available.
Editors
T.V. Raman, Dave Raggett.
Multimodal Interaction Working Group- Family:
- MMI
This document describes fundamental requirements for the specifications under development in the W3C Multimodal Interaction Activity. These requirements were derived from use case studies as discussed in Appendix A. They have been developed for use by the Multimodal Interaction Working Group (W3C Members only), but may also be relevant to other W3C working groups and related external standard activities.
The requirements cover general issues, inputs, outputs, architecture, integration, synchronization points, runtimes and deployments, but this document does not address application or deployment conformance rules.
Editors
Stéphane Maes, Vijay Saraswat.
Multimodal Interaction Working Group- Family:
- MMI
The W3C Multimodal Interaction Activity is developing specifications as a basis for a new breed of Web applications in which you can interact using multiple modes of interaction, for instance, using speech, hand writing, and key presses for input, and spoken prompts, audio and visual displays for output. This document describes several use cases for multimodal interaction and presents them in terms of varying device capabilities and the events needed by each use case to couple different components of a multimodal application.
Editors
Dave Raggett.
Multimodal Interaction Working Group- Family:
- MMI
RDB2RDF
Complete
This document describes R2RML, a language for expressing customized mappings from relational databases to RDF datasets.
Editors
Souripriya Das, Seema Sundara, Richard Cyganiak.
RDB2RDF Working Group- Family:
- RDB2RDF
This document defines a direct mapping from relational data to RDF.
Editors
Marcelo Arenas, Alexandre Bertails, Eric Prud'hommeaux, Juan Sequeda.
RDB2RDF Working Group- Family:
- RDB2RDF
Editors
Boris Villazón-Terrazas, Michael Hausenblas.
RDB2RDF Working Group- Family:
- RDB2RDF
Editors
Boris Villazón-Terrazas, Michael Hausenblas.
RDB2RDF Working Group- Family:
- RDB2RDF
In progress
These use-cases document the need to expose data from relational databases (RDB) as RDF on the Web of data, and so deliver a set of functional requirements for a standardized mapping language.
Editors
Eric Prud'hommeaux, Michael Hausenblas.
RDB2RDF Working Group- Family:
- RDB2RDF
Media Fragments
Complete
This document describes the Media Fragments 1.0 specification. It specifies the syntax for constructing media fragment URIs and explains how to handle them when used over the HTTP protocol. The syntax is based on the specification of particular field-value pairs that can be used in URI fragment and URI query requests to restrict a media resource to a certain fragment.
Editors
Raphaël Troncy, Erik Mannens, Silvia Pfeiffer, Davy Van Deursen.
Media Fragments Working Group- Family:
- Media Fragments
Available in:
日本語In progress
This document complements the Media Fragments 1.0 specification. It described various recipes for processing media fragments URI when used over the HTTP protocol.
Editors
Raphaël Troncy, Erik Mannens, Silvia Pfeiffer, Davy Van Deursen.
Media Fragments Working Group- Family:
- Media Fragments
This document describes use cases and requirements for the development of the Media Fragments 1.0 specification. It also specifies the syntax for constructing media fragment URIs and explains how to handle them when used over the HTTP protocol. It finally includes a technology survey for addressing fragments of multimedia document.
Editors
Raphaël Troncy, Erik Mannens.
Media Fragments Working Group- Family:
- Media Fragments
XForms
Complete
XForms is an XML application that represents the next generation of forms for the Web. XForms is not a free-standing document type, but is intended to be integrated into other markup languages, such as XHTML, ODF or SVG. An XForms-based web form gathers and processes XML data using an architecture that separates presentation, purpose and content. The underlying data of a form is organized into instances of data schema (though formal schema definitions are not required). An XForm allows processing of data to occur using three mechanisms:
-
a declarative model composed of formulae for data calculations and constraints, data type and other property declarations, and data submission parameters
-
a view layer composed of intent-based user interface controls
-
an imperative controller for orchestrating data manipulations, interactions between the model and view layers, and data submissions.
Thus, XForms accommodates form component reuse, fosters strong data type validation, eliminates unnecessary round-trips to the server, offers device independence and reduces the need for scripting.
XForms 1.1 refines the XML processing platform introduced by [XForms 1.0] by adding several new submission capabilities, action handlers, utility functions, user interface improvements, and helpful datatypes as well as a more powerful action processing facility, including conditional, iterated and background execution, the ability to manipulate data arbitrarily and to access event context information.
Editors
John Boyer.
Forms Working Group- Family:
- XForms
XForms is an XML application that represents the next generation of forms for the Web. This document specifies the requirements for XForms 1.1.
Editors
John Boyer, Roland Merrick.
Forms Working Group- Family:
- XForms
In progress
This specification defines how XPath can be used for addressing instance data nodes in binding expressions, to express constraints, and to specify calculations in XForms. This module is based on XPath 2.0, but an XPath 1.0 backwards compatibility mode is provided to ensure that nearly all XPath 1.0 expressions continue to deliver the same result with XPath 2.0.
This specification also defines the XForms Function Library which contains additional functions that are useful for creating forms.
Editors
Nick Van Den Bleeken, John Boyer.
Forms Working Group- Family:
- XForms
XForms 2.0 adds support for defining custom functions, variables, a pluggable expression language with extra functions (XPath 2.0), model-based switch and repeat, Attribute Value Templates, consuming and submitting JSON and CSV instance data, amongst other things.
Editors
John Boyer, L Klotz, Steven Pemberton, Nick Van Den Bleeken.
Forms Working Group- Family:
- XForms
XForms for HTML provides a set of attributes and script methods that can be used by the tags or elements of an HTML or XHTML web page to simplify the integration of data-intensive interactive processing capabilities from XForms.
Editors
John Boyer.
Forms Working Group- Family:
- XForms
The XForms Basic Profile describes a minimal level of XForms processing tailored to the needs of constrained devices and environments.
Editors
Micah Dubinko, T.V. Raman.
Forms Working Group- Family:
- XForms
Forms were introduced into HTML in 1993. Since then they have gone on to become a critical part of the Web. The existing mechanisms in HTML for forms are now outdated, and W3C has started work on developing an effective replacement. This document outlines the requirements for "XForms", W3C's name for the next generation of Web forms.
Editors
Micah Dubinko, Sebastian Schnitzenbaumer, Dave Raggett.
Forms Working Group- Family:
- XForms
Web Application Privacy Best Practices
Complete
This document describes privacy best practices for web applications, including those that might use device APIs.
Editors
Frederick Hirsch.
Devices and Sensors Working Group- Family:
- Web Application Privacy Best Practices
XML Schema
Complete
This document specifies the XML Schema Definition Language, which offers facilities for describing the structure and constraining the contents of XML documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in an XML vocabulary and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML document type definitions (DTDs). This specification depends on XML Schema Definition Language 1.1 Part 2: Datatypes.
Editors
Sandy Gao, Michael Sperberg-McQueen, Henry Thompson, Noah Mendelsohn, David Beech, Murray Maloney.
XML Schema Working Group- Family:
- XML Schema
XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML, provides a superset of the capabilities found in XML document type definitions (DTDs) for specifying datatypes on elements and attributes.
Editors
David Peterson, Sandy Gao, Ashok Malhotra, Michael Sperberg-McQueen, Henry Thompson, Paul V. Biron.
XML Schema Working Group- Family:
- XML Schema
Editors
David Peterson, Michael Sperberg-McQueen.
XML Schema Working Group- Family:
- XML Schema
Editors
Michael Sperberg-McQueen.
XML Schema Working Group- Family:
- XML Schema
Editors
Jonathan Calladine, George Cowe, Paul Downey, Yves Lafon.
XML Schema Patterns for Databinding Working Group- Family:
- XML Schema
Editors
Jonathan Calladine, George Cowe, Paul Downey, Yves Lafon.
XML Schema Patterns for Databinding Working Group- Family:
- XML Schema
The RDF and OWL Recommendations use the simple types from XML Schema. This document addresses three questions left unanswered by these Recommendations: Which URIref should be used to refer to a user defined datatype? Which values of which XML Schema simple types are the same? How to use the problematic xsd:duration in RDF and OWL? In addition, we further describe how to integrate OWL DL with user defined datatypes (in appendix B).
Editors
Jeremy Carroll, Jeff Pan.
Semantic Web Best Practices and Deployment Working Group- Family:
- XML Schema
XML Schema 1.0 did not anticipate new versions of XML, and mandated XML 1.0 documents as the starting point for schema-validity assessment. Some users and specifications would like to use XML Schema processors which process XML 1.1 documents, and some implementors of XML Schema processors would like to provide XML 1.1 support.
This Note suggests an implementation strategy for implementors to adopt to enable users and specifications to get such support in a consistent way. All aspects of XML Schema which are liable to re-interpretation as a result of changes in XML 1.1 are discussed.
An implementation of schema-validity assessment employing such a strategy is strictly speaking non-conformant to the current version of the XML Schema specification. The XML Schema WG none-the-less believes that interoperability will best be served by such non-conformant processors being made available to users, until such time as a subsequent version of XML Schema addressing this issue normatively is approved.
Editors
Henry Thompson.
XML Schema Working Group- Family:
- XML Schema
Add content here.
Editors
Henry Thompson, David Beech, Murray Maloney, Noah Mendelsohn.
XML Schema Working Group- Family:
- XML Schema
XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes.
Editors
Paul V. Biron, Ashok Malhotra.
XML Schema Working Group- Family:
- XML Schema
Add content here.
Editors
David Fallside, Priscilla Walmsley.
XML Schema Working Group- Family:
- XML Schema
Available in:
portuguêsEditors
Ashok Malhotra, Murray Maloney.
XML Schema Working GroupUNKNOWN WORKING GROUP
- Family:
- XML Schema
In progress
XML Schema: Component Designators defines a scheme for identifying XML Schema components as specified by XML Schema Part 1: Structures and XML Schema Part 2: Datatypes.
Editors
Mary Holstege, Asir Vedamuthu.
XML Schema Working Group- Family:
- XML Schema
Widgets
Complete
This specification defines the widget URI scheme that is used to address resources inside a widget package.
Editors
Marcos Caceres.
(historical) Web Applications Working Group- Family:
- Widgets
This document lists the design goals and requirements that specifications would need to address in order to standardize various aspects of widgets.
Editors
Marcos Caceres.
(historical) Web Applications Working Group- Family:
- Widgets
In progress
This document surveys a group of market-leading widget user agents with the aim to inform the requirements of the Widgets 1.0: Requirements document. The survey exposes commonalities and fragmentation across widget user agents, and discusses how fragmentation currently affects, amongst other things, authoring, security, ../distribution and deployment, internationalisation and the device-independence of widgets. The document concludes by making a set of recommendations on what aspects of widgets require standardization to reduce fragmentation to ultimately standardize a cross-platform widget solution.
Editors
Marcos Caceres.
Web Application Formats Working Group- Family:
- Widgets
SOAP
Complete
This document specifies how SOAP should bind to a messaging system that supports the Java Message Service (JMS) [Java Message Service]. Binding is specified for both SOAP 1.1 [SOAP 1.1] and SOAP 1.2 [SOAP 1.2 Messaging Framework] using the SOAP 1.2 Protocol Binding Framework.
Editors
Phil Adams, Peter Easton, Eric Johnson, Roland Merrick, Mark Phillips.
SOAP-JMS Binding Working Group- Family:
- SOAP
SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.
Editors
David Orchard.
XML Protocol Working Group- Family:
- SOAP
SOAP Version 1.2 Part 0: Primer (Second Edition) is a non-normative document intended to provide an easily understandable tutorial on the features of SOAP Version 1.2. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications. This second edition includes additional material on the SOAP Message Transmission Optimization Mechanism (MTOM), the XML-binary Optimized Packaging (XOP) and the Resource Representation SOAP Header Block (RRSHB) specifications.
Editors
Nilo Mitra, Yves Lafon.
XML Protocol Working Group- Family:
- SOAP
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, ../distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework [SOAP Part 1].
Editors
Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon.
XML Protocol Working Group- Family:
- SOAP
This document draws on assertions found in the SOAP Version 1.2 specifications [SOAP Part 1], [SOAP Part 2], and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor.
A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite, 2007 04 27. It is incorrect to claim to be compliant with the SOAP Version 1.2 specifications merely by passing successfully all the tests provided in this test suite. It is also incorrect to claim that an implementation is non compliant with the SOAP Version 1.2 specifications based on its failure to pass one or more of the tests in this test suite.
Editors
Hugo Haas, Oisin Hurley, Anish Karmarkar, Jeff Mischkinsky, Mark Jones, Lynne R. Thompson, Richard D. Martin.
XML Protocol Working Group- Family:
- SOAP
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, ../distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols.
Editors
Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau, Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon.
XML Protocol Working Group- Family:
- SOAP
SOAP Version 1.1 provides an HTTP binding for exchanging a request and a response. This binding provides a "request optional response" refinement that enables an HTTP response with status code 202 to have a SOAP envelope or to be empty.
Editors
David Orchard.
Web Services Addressing Working Group- Family:
- SOAP
This document addresses the need to indicate the content-type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected content-type(s) associated with binary element content. It is expected that the additional information about the content-type will be used for optimizing the handling of binary data that is part of a Web services message.
Editors
Anish Karmarkar, Ümit Yalçinalp.
XML Protocol Working GroupWeb Services Description Working Group
- Family:
- SOAP
This document describes the semantics and serialization of a SOAP header block for carrying resource representations in SOAP messages.
Editors
Anish Karmarkar, Martin Gudgin, Yves Lafon.
XML Protocol Working Group- Family:
- SOAP
This document defines the XML-binary Optimized Packaging (XOP) convention, a means of more efficiently serializing XML Infosets that have certain types of content.
Editors
Martin Gudgin, Noah Mendelsohn, Mark Nottingham, Hervé Ruellan.
XML Protocol Working Group- Family:
- SOAP
Available in:
portuguêsThis document describes an abstract feature and a concrete implementation of it for optimizing the transmission and/or wire format of SOAP messages. The concrete implementation relies on the [XML-binary Optimized Packaging] format for carrying SOAP messages.
Editors
Martin Gudgin, Noah Mendelsohn, Mark Nottingham, Hervé Ruellan.
XML Protocol Working Group- Family:
- SOAP
This document defines a SOAP feature that represents an abstract model for SOAP attachments. It provides the basis for the creation of SOAP bindings that transmit such attachments along with a SOAP envelope, and provides for reference of those attachments from the envelope. SOAP attachments are described using the notion of a compound document structure consisting of a primary SOAP message part and zero or more related documents parts known as attachments.
Editors
Henrik Frystyk Nielsen, Hervé Ruellan.
XML Protocol Working Group- Family:
- SOAP
This document lists and provides answers to some frequently asked questions about the design decisions behind the choice of include mechanism by the XML Protocol Working Group during construction of XML-binary Optimized Packaging (XOP). For more information about XOP, see the Working Group Home Page.
Editors
Michael Mahan.
XML Protocol Working Group- Family:
- SOAP
SOAP 1.2 intermediaries have some license when reserializing messages that pass through them. This document defines a transformation algorithm that renders all semantically equivalent SOAP messages identically. The transformation may be used in conjunction with an XML canonicalization algorithm prior to the generation of a message digest in producing XML digital signatures that are sufficiently robust to survive passage through one or more SOAP intermediaries.
Editors
Martin Gudgin, Marc Hadley.
XML Protocol Working Group- Family:
- SOAP
This document describes the SOAP Usage Scenarios and how they may be implemented using the SOAP 1.2 specification.
Editors
John Ibbotson.
XML Protocol Working Group- Family:
- SOAP
This document describes the XML Protocol Working Group's requirements for the XML Protocol (XMLP) specification.
Editors
Alex Ceponkus, Paul Cotton, David Ezell, David Fallside, Martin Gudgin, Oisin Hurley, John Ibbotson, Alex Miłowski, Kevin Mitchell, Jean-Jacques Moreau, Eric Newcomer, Henrik Frystyk Nielsen, Bob Lojek, Mark Nottingham, Waqar Sadiq, Stuart Williams, Amr Yassin.
XML Protocol Working Group- Family:
- SOAP
This document is meant to be an illustration of the SOAP 1.2 Protocol Binding Framework applied to a well known internet transport mechanism, Email, specifically rfc2822.
Editors
Highland Mary Mountain, Jacek Kopecky, Stuart Williams, Glen Daniels, Noah Mendelsohn.
XML Protocol Working Group- Family:
- SOAP
XSL
Complete
This specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. It consists of two parts:
-
a language for transforming XML documents (XSLT), and
-
an XML vocabulary for specifying formatting semantics.
An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary.
Editors
Anders Berglund.
XSLT Working Group- Family:
- XSL
This specification defines the features and syntax for the Extensible Stylesheet Language (XSL), a language for expressing stylesheets. It consists of two parts:
-
a language for transforming XML documents (XSLT), and
-
an XML vocabulary for specifying formatting semantics.
An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary.
Editors
Sharon Adler, Anders Berglund, Jeffrey Caruso, Stephen Deach, Tony Graham, Paul Grosso, Eduardo Gutentag, Alex Miłowski, Scott Parnell, Jeremy Richman, Steve Zilles.
XSLT Working Group- Family:
- XSL
In progress
This document describes initial design notes for version 2.0 of the Formatting Object (FO) part of the Extensible Stylesheet Language (XSL).
Editors
Dave Pawson.
XML Print and Page Layout Working Group- Family:
- XSL
This document enumerates the collected requirements for a 2.0 version of XSL-FO.
Editors
Klaas Bals.
XSLT Working Group- Family:
- XSL
Web Services
Complete
This specification describes a protocol that allows Web services to subscribe to or accept subscriptions for notification messages.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This specification extends the WS-Transfer specification to enable clients to retrieve and manipulate parts or fragments of a WS-Transfer enabled resource without needing to include the entire XML representation in a message exchange.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This specification defines two WS-Policy assertions that can be used to advertise the requirement to use a certain version of SOAP in message exchanges.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This specification describes a general SOAP-based protocol for enumerating a sequence of XML elements from a SOAP enabled information source.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This specification describes a general SOAP-based protocol for accessing XML representations of Web service-based resources.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This specification defines how metadata associated with a Web service endpoint can be represented as resources, how metadata can be embedded in endpoint references, how metadata could be retrieved from a metadata resource, and how metadata associated with implicit features can be advertised.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This specification describes a mechanism by which an endpoint can advertise the structure and contents of the events it might generate.
Editors
Doug Davis, Ashok Malhotra, Katy Warr, Wu Chou.
Web Services Resource Access Working Group- Family:
- Web Services
This document describes requirements for internationalizing Web services.
Editors
Addison Phillips.
Internationalization Working Group- Family:
- Web Services
Describes internationalization usage patterns and scenarios for Web services. Provides additional guidance for implementers of Web service technologies, suggesting methods for dealing with general international interoperability issues in services and service descriptions. Provides a template for Web service designers to implement international capabilities in their services.
Editors
Debasish Banerjee, Martin Dürst, Michael McKenna, Addison Phillips, Takao Suzuki, Tex Texin, Mary Trumble, Andrea Vine, Kentaro Noji.
Internationalization Working Group- Family:
- Web Services
This document describes the life cycle of a Web service, and of the processing of a request by a Web service.
Editors
Hao He, Mark Potts, Igor Sedukhin.
Web Services Architecture Working Group- Family:
- Web Services
This document is a glossary of Web services terms defined and used in the Web Services Architecture [WS Arch]. It is intended for use by Web services spefications in order to refer to a common coherent framework.
Editors
Hugo Haas, Allen Brown.
Web Services Architecture Working Group- Family:
- Web Services
This document defines the Web Services Architecture. It identifies the functional components and defines the relationships among those components to effect the desired properties of the overall architecture.
Editors
David Booth, Hugo Haas, Francis McCabe, Eric Newcomer, Mike Champion, Christopher Ferris, David Orchard.
Web Services Architecture Working Group- Family:
- Web Services
This document describes the Web Service Architecture use cases and Usage Scenarios.
It is a collection of use cases and usage scenarios which illustrate the use of Web services. They are used to generate requirements for the Web services architecture, as well as to evaluate existing technologies.
Editors
Hao He, Hugo Haas, David Orchard.
Web Services Architecture Working Group- Family:
- Web Services
This document describes a set of requirements for a standard reference architecture for Web services developed by the Web Services Architecture Working Group. These requirements are intended to guide the development of the reference architecture and provide a set of measurable constraints on Web services implementations by which conformance can be determined.
Editors
Daniel Austin, Abbie Barbir, Christopher Ferris, Sharad Garg.
Web Services Architecture Working Group- Family:
- Web Services
InkML
Complete
This document describes the syntax and semantics for the Ink Markup Language for use in the W3C Multimodal Interaction Framework as proposed by the W3C Multimodal Interaction Activity. The Ink Markup Language serves as the data format for representing ink entered with an electronic pen or stylus. The markup allows for the input and processing of handwriting, gestures, sketches, music and other notational languages in applications. It provides a common format for the exchange of ink data between components such as handwriting and gesture recognizers, signature verifiers, and other ink-aware modules.
Editors
Stephen Watt, Tom Underhill.
Multimodal Interaction Working Group- Family:
- InkML
This document describes requirements for the Ink Markup Language that will be used in the multimodal interaction framework as proposed by the W3C Multimodal Interaction Working Group. The Ink Markup Language will serve as the data format for representing ink entered with an electronic pen or stylus in a multimodal system. The markup will allow for the input and processing of handwriting, gestures, sketches, music and other notational languages in web-based multimodal applications. In the context of the W3C Multimodal Interaction Framework, the markup provides a common format for the exchange of ink data between components such as handwriting and gesture recognizers, signature verifiers, and other ink-aware modules.
Editors
Yi-Min Chee, Sai Prasad.
Multimodal Interaction Working Group- Family:
- InkML
CCXML
Complete
The Call Control Extensible Markup Language (CCXML) provides declarative markup to describe telephony call control. CCXML can be used in conjunction with a dialog system such as VoiceXML.
Editors
Paolo Baggia, Mark Scott.
Voice Browser Working Group- Family:
- CCXML
Working with Time Zones
Complete
Discusses some of the problems encountered when working with the date, time, and dateTime values from XML Schema when those value include (or omit) time zone offsets. Many W3C technologies rely on date and time types.
Editors
Addison Phillips.
Internationalization Working Group- Family:
- Working with Time Zones
Voice Browsers
Complete
VoiceXML 2.1 specifies a set of features commonly implemented by Voice Extensible Markup Language platforms. This specification is designed to be fully backwards-compatible with VoiceXML 2.0 [VXML2]. This specification describes only the set of additional features.
Editors
Matt Oshry, RJ Auburn, Paolo Baggia, Michael Bodell, David Burke, Daniel Burnett, Jerry Carter, Scott McGlashan, Alex Lee, Brandon Porter, Kenneth Rehor.
Voice Browser Working Group- Family:
- Voice Browsers
This document specifies VoiceXML, the Voice Extensible Markup Language. VoiceXML is designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed initiative conversations. Its major goal is to bring the advantages of Web-based development and content delivery to interactive voice response applications.
Editors
Scott McGlashan, Daniel Burnett, Jerry Carter, Peter Danielsen, Jim Ferrans, Andrew Hunt, Bruce Lucas, Brandon Porter, Kenneth Rehor, Steph Tryphonas.
Voice Browser Working Group- Family:
- Voice Browsers
Available in:
françaisIn progress
VoiceXML 3.0 is a modular XML language for creating interactive media dialogs that feature synthesized speech, recognition of spoken and DTMF key input, telephony, mixed initiative conversations, and recording and presentation of a variety of media formats including digitized audio, and digitized video. The primary goal of the spec is to bring the advantages of Web-based development and content delivery to interactive voice response applications.
Editors
Scott McGlashan, Daniel Burnett, Rahul Akolkar, RJ Auburn, Paolo Baggia, Michael Bodell, Jerry Carter, Mangesh Deshmukh, Matt Oshry, Kenneth Rehor, Xu Yang, Milan Young, Rafah Hosn.
Voice Browser Working Group- Family:
- Voice Browsers
The W3C Voice Browser working group aims to develop specifications to enable access to the Web using spoken interaction. This document is part of a set of requirement studies for voice browsers, and provides details of the requirements for marking up spoken dialogs.
Editors
Jeff Hoepfinger.
Voice Browser Working Group- Family:
- Voice Browsers
Mobile Best Practices
Complete
This document specifies best practices for the development and delivery of Web applications on mobile devices.
Editors
Adam Connors, Bryan Sullivan.
Mobile Web Best Practices Working Group- Family:
- Mobile Best Practices
This document identifies the issues surrounding use of transforming proxies in the delivery of Web content. It does not comment on the techniques that cause these issues, it merely identifies them in order to inform the requirements of the Content Transformation Guidelines document. That document is to offer recommendations as to how components of the delivery context can cooperate to achieve, at a minimum, a functional user experience.
Editors
Jo Rabin, Andrew Swainston.
Mobile Web Best Practices Working Group- Family:
- Mobile Best Practices
The purpose of the Protocol for Web Description Resources (POWDER) is to provide a means for individuals or organizations to describe a group of resources through the publication of machine-readable metadata, as motivated by the POWDER Use Cases [USECASES]. This document details the creation and lifecycle of Description Resources (DRs), which encapsulate such metadata. These are typically represented in a highly constrained XML dialect that is relatively human-readable. The meaning of such DRs are underpinned by formal semantics, accessible by performing a GRDDL Transform.
Editors
Phil Archer, Kevin Smith, Andrea Perego.
Protocol for Web Description Resources (POWDER) Working Group- Family:
- Mobile Best Practices
This document underpins the Protocol for Web Description Resources (POWDER). It describes how the relatively simple operational format of a POWDER document can be transformed through two stages: first into a more tightly constrained XML format (POWDER-BASE), and then into an RDF/OWL encoding (POWDER-S) that may be processed by Semantic Web tools. Such processing is only possible, however, if tools implement the semantic extension defined within this document. The formal semantics of POWDER are best understood after the reader is acquainted with the Description Resources [DR] and Grouping of Resources [GROUP] documents.
Editors
Stasinos Konstantopoulos, Phil Archer.
Protocol for Web Description Resources (POWDER) Working Group- Family:
- Mobile Best Practices
The Protocol for Web Description Resources (POWDER) facilitates the publication of descriptions of multiple resources such as all those available from a Web site. This document describes how sets of IRIs can be defined such that descriptions or other data can be applied to the resources obtained by dereferencing IRIs that are elements of the set. IRI sets are defined as XML elements with relatively loose operational semantics. This is underpinned by the formal semantics of POWDER which include a semantic extension, defined separately. A GRDDL transform is associated with the POWDER namespace that maps the operational to the formal semantics.
Editors
Phil Archer, Andrea Perego, Kevin Smith.
Protocol for Web Description Resources (POWDER) Working Group- Family:
- Mobile Best Practices
The mobileOK scheme allows content providers to promote their content as being suitable for use on very basic mobile devices.
Editors
Jo Rabin, Phil Archer.
Mobile Web Best Practices Working Group- Family:
- Mobile Best Practices
Available in:
DeutschThis technical report describes the similarities and differences between the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices 1.0.
Editors
Alan Chuter, Yeliz Yesilada.
Accessibility Education and Outreach Working Group (EOWG)Mobile Web Best Practices Working Group
- Family:
- Mobile Best Practices
This document offers guidance in the form of simple guidelines to follow to create device-independent tests for Web technologies.
Editors
Dominique Hazaël-Massieux, Carmelo Montanez.
Mobile Web Test Suites Working Group- Family:
- Mobile Best Practices
This document defines the tests that provide the basis for making a claim of W3C® mobileOK™ Basic conformance and are based on W3C Mobile Web Best Practices [Best Practices]. The details of how to claim mobileOK conformance will be described separately. Providers of content which passes the tests have taken some steps to provide a functional user experience for users of basic mobile devices whose capabilities at least match those of the Default Delivery Context (DDC).
mobileOK Basic primarily assesses basic usability, efficiency and interoperability. It does not address the important goal of assessing whether users of more advanced devices enjoy a richer user experience than is possible using the DDC.
Editors
Sean Owen, Jo Rabin.
Mobile Web Best Practices Working Group- Family:
- Mobile Best Practices
This document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices.
The recommendations refer to delivered content and not to the processes by which it is created, nor to the devices or user agents to which it is delivered.
It is primarily directed at creators, maintainers and operators of Web sites. Readers of this document are expected to be familiar with the creation of Web sites, and to have a general familiarity with the technologies involved, such as Web servers and HTTP. Readers are not expected to have a background in mobile-specific technologies.
Editors
Jo Rabin, Charles McCathieNevile.
Mobile Web Best Practices Working Group- Family:
- Mobile Best Practices
Available in:
françaisThe Scope of Mobile Web Best Practices identifies the nature of problems that made the Web unattractive for most mobile users, and outlines the scope of work that needed to be undertaken.
Editors
Phil Archer, Edward Mitukiewicz.
Mobile Web Best Practices Working Group- Family:
- Mobile Best Practices
SSML
Complete
Editors
Daniel Burnett, Zhi Wei Shuang.
Voice Browser Working Group- Family:
- SSML
Available in:
日本語Editors
Daniel Burnett, Paolo Baggia, An Buyle, Ellen Eide, Luc Van Tichelen.
Voice Browser Working Group- Family:
- SSML
Editors
Daniel Burnett, Mark Walker, Andrew Hunt.
Voice Browser Working Group- Family:
- SSML
In progress
Editors
Daniel Burnett, Zhi Wei Shuang.
Voice Browser Working Group- Family:
- SSML
XLink
Complete
This specification defines the XML Linking Language (XLink) Version 1.1, which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.
Editors
Steven DeRose, Eve Maler, David Orchard, Norman Walsh.
XML Core Working Group- Family:
- XLink
This document describes some useful changes that could be incorporated into an XLink 1.1 Specification.
Editors
Norman Walsh.
XML Core Working Group- Family:
- XLink
This specification defines the XML Linking Language (XLink), which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links.
Editors
Steven DeRose, Eve Maler, David Orchard.
XML Linking Working Group- Family:
- XLink
The interaction of XLink linking elements and styling has not previously been carefully described. This note, the result of an XML Linking/XSL joint task force, attempts to rectify that oversight by providing a clear conceptual model for linking and styling and suggestions for the practical application of that model using current W3C Recommendations (and Working Drafts, Candidate Recommendations, and Proposed Recommendations).
Editors
Norman Walsh.
XML Linking Working Group- Family:
- XLink
Both XLink [XLink] and RDF [RDF] provide a way of asserting relations between resources. RDF is primarily for describing resources and their relations, while XLink is primarily for specifying and traversing hyperlinks. However, the overlap between the two is sufficient that a mapping from XLink links to statements in an RDF model can be defined. Such a mapping allows XLink elements to be harvested as a source of RDF statements. XLink links (hereafter, "links") thus provide an alternate syntax for RDF information that may be useful in some situations.
This Note specifies such a mapping, so that links can be harvested and RDF statements generated. The purpose of this harvesting is to create RDF models that, in some sense, represent the intent of the XML document. The purpose is not to represent the XLink structure in enough detail that a set of links could be round-tripped through an RDF model.
Editors
Ron Daniel.
UNKNOWN WORKING GROUP- Family:
- XLink
Editors
Steven DeRose.
XML Linking Working Group- Family:
- XLink
Editors
Eve Maler, Steven DeRose.
XML Core Working GroupXML Linking Working Group
- Family:
- XLink
WebCGM
Complete
WebCGM 2.1 specification refines and completes the features of the major WebCGM 2.0 release.
Editors
Benoit Bezaire, Lofton Henderson.
WebCGM Working Group- Family:
- WebCGM
Editors
Chris Lilley.
UNKNOWN WORKING GROUP- Family:
- WebCGM
QA Framework
Complete
Editors
Dominique Hazaël-Massieux, Marcos Caceres.
Mobile Web Test Suites Working Group- Family:
- QA Framework
The definition and provision of metadata has proved helpful in a variety of ways during the test development and test execution processes. This document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite.
Editors
Patrick Curran, Karl Dubost.
Quality Assurance Working Group- Family:
- QA Framework
The QA Handbook (QAH) is a non-normative handbook about the process and operational aspects of certain quality assurance practices of W3C's Working Groups, with particular focus on testability and test topics. It is intended for Working Group chairs and team contacts. It aims to help them to avoid known pitfalls and benefit from experiences gathered from the W3C Working Groups themselves. It provides techniques, tools, and templates that should facilitate and accelerate their work. This document is one of the QA Framework (QAF) family of documents of the Quality Assurance (QA) Activity. QAF includes the other in-progress specification, Specification Guidelines, Test Development FAQ, plus a handful of test- and other QA-related notes, advanced topics, and Wiki page collections.
Editors
Lofton Henderson.
Quality Assurance Working Group- Family:
- QA Framework
This document details and deepens some of the most important concepts related to conformance when designing a specification. It is a companion document of QA Specification Guidelines. It analyzes how design decisions of a specification's conformance model may affect its implementability and the interoperability of its implementations.
Editors
Dominique Hazaël-Massieux, Lynne Rosenthal.
Quality Assurance Working Group- Family:
- QA Framework
The goal of this document is to help W3C editors write better specifications, by making a specification easier to interpret without ambiguity and clearer as to what is required in order to conform. It focuses on how to define and specify conformance. It also addresses how a specification might allow variation among conforming implementations. The document presents guidelines or requirements, supplemented with good practices, examples and techniques.
Editors
Karl Dubost, Lynne Rosenthal, Dominique Hazaël-Massieux, Lofton Henderson.
Quality Assurance Working Group- Family:
- QA Framework
Mobile Web for Social Development
Complete
Editors
Stéphane Boyera.
Mobile Web For Social Development (MW4D) Interest Group- Family:
- Mobile Web for Social Development
PICS
Complete
Editors
Christopher Evans, Alex Hopmann, Martin PreslerMarshall, Paul Resnick.
UNKNOWN WORKING GROUP- Family:
- PICS
Editors
Yanghua Chu, Philip DesAutels, Brian LaMacchia, Peter Lipp.
UNKNOWN WORKING GROUP- Family:
- PICS
Editors
Tim Krauskopf, Jim Miller, Paul Resnick, Win Treese.
UNKNOWN WORKING GROUP- Family:
- PICS
Editors
Jim Miller, Paul Resnick, David Singer.
UNKNOWN WORKING GROUP- Family:
- PICS
SML
Complete
The Service Modeling Language specification extends the Extensible Mark-up Language and XML Schema with a mechanism for incorporating into XML documents references to other documents or document fragments. This technical note addresses the construction of an SML reference scheme based on the XML Linking Language.
Editors
Pratul Dublish, Len Charest, Virginia Smith.
Service Modeling Language Working Group- Family:
- SML
Editors
Len Charest.
Service Modeling Language Working Group- Family:
- SML
Editors
Valentina Popescu, Virginia Smith.
Service Modeling Language Working Group- Family:
- SML
Editors
Valentina Popescu, Virginia Smith.
Service Modeling Language Working Group- Family:
- SML
POWDER
Complete
The document describes and presents test cases for the Protocol for Web Description Resources (POWDER). The test cases aim to indicate the correct formats of POWDER documents and illustrate various crucial aspects on the usage of POWDER documents, such as locating a document and infering information from it.
Editors
Antonis Kukurikos, Phil Archer.
Protocol for Web Description Resources (POWDER) Working Group- Family:
- POWDER
POWDER — the Protocol for Web Description Resources — provides a mechanism to describe and discover Web resources and helps the users to make a decision whether a given resource is of interest. There are a variety of use cases: from providing a better means to describing Web resources and creating trustmarks to aiding content discovery, child protection and Semantic Web searches.
There are two varieties of POWDER: a complex, semantically rich variety, called POWDER-S, and a much simpler version, just called POWDER, which is intended as the primary transport mechanism for Description Resources. POWDER-S can be generated automatically from POWDER.
Editors
Kai Scheppe.
Protocol for Web Description Resources (POWDER) Working Group- Family:
- POWDER
This document sets out the use cases and requirements that have motivated the development of the Protocol for Web Description Resources (POWDER). The use cases address social and commercial needs to provide information about groups of Web resources, such as those available from a Web site, to aid the annotation and/or personalization of content for end users in varying delivery contexts.
Editors
Phil Archer.
Protocol for Web Description Resources (POWDER) Working Group- Family:
- POWDER
egov
Complete
Add content here.
Editors
Suzanne Acar, José Manuel Alonso, Kevin Novak.
eGovernment Interest Group- Family:
- egov
In progress
These guidelines are designed to help governments open and share their data. These straightforward steps emphasize standards and methodologies to encourage publication of government data, allowing the public to use this data in new and innovative ways.
Editors
Daniel Bennett, Adam Harvey.
eGovernment Interest Group- Family:
- egov
SKOS
Complete
This document defines the Simple Knowledge Organization System (SKOS), a common data model for sharing and linking knowledge organization systems via the Web.
Many knowledge organization systems, such as thesauri, taxonomies, classification schemes and subject heading systems, share a similar structure, and are used in similar applications. SKOS captures much of this similarity and makes it explicit, to enable data and technology sharing across diverse applications.
The SKOS data model provides a standard, low-cost migration path for porting existing knowledge organization systems to the Semantic Web. SKOS also provides a light weight, intuitive language for developing and sharing new knowledge organization systems. It may be used on its own, or in combination with formal knowledge representation languages such as the Web Ontology language (OWL).
This document is the normative specification of the Simple Knowledge Organization System. It is intended for readers who are involved in the design and implementation of information systems, and who already have a good understanding of Semantic Web technology, especially RDF and OWL.
For an informative guide to using SKOS, see the SKOS Primer.
Editors
Alistair Miles, Sean Bechhofer.
Semantic Web Deployment Working Group- Family:
- SKOS
Knowledge organisation systems, such as taxonomies, thesauri or subject heading lists, play a fundamental role in information structuring and access. The Semantic Web Deployment Working Group aims at providing a model for representing such vocabularies on the Semantic Web: SKOS (Simple Knowledge Organisation System).
This document presents the preparatory work for a future version of SKOS. It lists representative use cases, which were obtained after a dedicated questionnaire was sent to a wide audience. It also features a set of fundamental or secondary requirements derived from these use cases, that will be used to guide the design of SKOS.
Editors
Antoine Isaac, Jon Phipps, Daniel Rubin.
Semantic Web Deployment Working Group- Family:
- SKOS
SKOS—Simple Knowledge Organization System—provides a model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, and other similar types of controlled vocabulary. As an application of the Resource Description Framework (RDF), SKOS allows concepts to be composed and published on the World Wide Web, linked with data on the Web and integrated into other concept schemes.
This document is a user guide for those who would like to represent their concept scheme using SKOS.
In basic SKOS, conceptual resources (concepts) are identified with URIs, labelled with strings in one or more natural languages, documented with various types of note, semantically related to each other in informal hierarchies and association networks, and aggregated into concept schemes.
In advanced SKOS, conceptual resources can be mapped across concept schemes and grouped into labelled or ordered collections. Relationships between concept labels can be specified. Finally, the SKOS vocabulary itself can be extended to suit the needs of particular communities of practice or combined with other modelling vocabularies.
This document is a companion to the SKOS Reference, which gives the normative reference on SKOS.
Editors
Antoine Isaac, Ed Summers.
Semantic Web Deployment Working Group- Family:
- SKOS
Device Description
Complete
Web content delivered to mobile devices usually benefits from being tailored to take into account a range of factors such as screen size, markup language support and image format support. Such information is stored in "Device Description Repositories" (DDRs).
This document describes a simple API for access to DDRs, in order to ease and promote the development of Web content that adapts to its Delivery Context.
Editors
Jo Rabin, Jose Manuel Cantera Fonseca, Rotan Hanrahan, Ignacio Marin.
Mobile Web Initiative Device Description Working Group- Family:
- Device Description
This document describes the Device Description Repository Core Vocabulary for Content Adaptation in the Mobile Web, described in the charter of the Device Descriptions Working Group, as well as the process by which the Vocabulary was defined.
Editors
Jo Rabin, Andrea Trasatti, Rotan Hanrahan.
Mobile Web Initiative Device Description Working Group- Family:
- Device Description
This document details use cases for a Device Descriptions Repository (DDR). In order to realize these use cases, certain behaviors will be expected of a DDR: these behaviors are determined and listed as requirements.
This Working Group Note forms one of the deliverables of the W3C Mobile Web Initiative Device Description Working Group. The requirements in this document are derived from the listed use-cases as well as information in the Device Description Landscape [DDLAND] and Device Description Ecosystem [DDECO] documents.
Editors
Kevin Smith, David Sanders.
Mobile Web Initiative Device Description Working Group- Family:
- Device Description
This W3C Note describes the business models surrounding the creation, maintenance and use of device descriptions. It identifies the main actors in the current model, explores their motivations for participating, identifies the costs associated with participation and the benefits that accrue to participants.
It is shown in this Note that the current model is incomplete, partly because of the absence of a common repository that can address the needs of the various actors. A complete model is postulated, on the assumption of the existence of a common repository, from which is derived some key requirements upon such a repository to ensure the success of the model.
This Note should be read in conjunction with the DDWG Landscape document, which provides details of the particular technologies and actors currently engaged in work related to device descriptions. This Note, together with the Landscape document, provides input to the DDWG Requirements document.
Editors
Rotan Hanrahan.
Mobile Web Initiative Device Description Working Group- Family:
- Device Description
Developing Web content for mobile devices is more challenging than developing for the desktop Web. Compared to desktop Web clients, mobile Web devices come in a much wider range of shapes, sizes and capabilities. The mobile Web developer relies upon accurate device descriptions in order to dynamically adapt content to suit the client.
This Note describes what efforts the W3C and other organizations are doing in order to provide accurate device descriptions. This Note should be read in conjunction with the DDWG Ecosystem [DDWG-Ecosystem] document.
This Note, together with the Ecosystem document, provides input to the proposed DDWG Requirements document as described in the DDWG Charter [DDWG-Charter]
Editors
Emmanuel Nkeze, Gavin James Pearce, Matt Womer.
Mobile Web Initiative Device Description Working Group- Family:
- Device Description
In progress
Add content here.
Editors
Jose Manuel Cantera Fonseca.
Mobile Web Initiative Device Description Working Group- Family:
- Device Description
SMIL
Complete
This document specifies the third version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 3.0 has the following design goals:
- Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL, an author may describe the temporal behaviour of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen.
- Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL components are used for integrating timing into XHTML [XHTML10] and into SVG [SVG].
- Extend the functionalities contained in the SMIL 2.1 [SMIL21] into new or revised SMIL 3.0 modules.
- Define new SMIL 3.0 Profiles incorporating features useful within the industry.
Editors
Dick Bulterman.
SYMM Working Group- Family:
- SMIL
This document specifies the second version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL 2.1 has the following design goals:
- Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL, an author can describe the temporal behaviour of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen.
- Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL components are used for integrating timing into XHTML [XHTML10] and into SVG [SVG].
- Extend the functionalities contained in the SMIL 2.0 [SMIL20] into new or revised SMIL 2.1 modules.
- Define new SMIL 2.1 Mobile Profiles incorporating features useful within the mobile industry.
Editors
Thierry Michel, Guido Grassel, Antti Koivisto, Nabil Layaida, Jack Jansen, Sjoerd Mullender, Daniel Zucker, Dick Bulterman.
SYMM Working Group- Family:
- SMIL
This is a W3C Recommendation of a specification of animation functionality for XML documents. It describes an animation framework as well as a set of base XML animation elements suitable for integration with XML documents. It is based upon the SMIL 1.0 timing model, with some extensions, and is a true subset of SMIL 2.0. This provides an intermediate stepping stone in terms of implementation complexity, for applications that wish to have SMIL-compatible animation but do not need or want time containers.
Editors
Patrick Schmitz, Aaron Cohen.
SVG Working GroupSYMM Working Group
- Family:
- SMIL
Editors
Patrick Schmitz, Ted Wugofski, Warner ten Kate.
SYMM Working Group- Family:
- SMIL
Editors
Philipp Hoschka.
SYMM Working Group- Family:
- SMIL
PLS
Complete
Editors
Paolo Baggia.
Voice Browser Working Group- Family:
- PLS
Available in:
日本語Best Practices for XML Internationalization
Complete
Provides a set of guidelines for developing XML documents and schemas that are properly internationalized, aimed at both developers of XML applications and authors of XML content.
Editors
Yves Savourel, Jirka Kosek, Richard Ishida.
Internationalization Tag Set (ITS) Working Group- Family:
- Best Practices for XML Internationalization
Available in:
françaisWeb Services Policy
Complete
Web Services Policy 1.5 - Guidelines for Policy Assertion Authors is intended to provide guidance for Assertion Authors that will work with the Web Services Policy 1.5 - Framework [Web Services Policy Framework] and Web Services Policy 1.5 - Attachment [Web Services Policy Attachment] specifications to create domain specific assertions. The focus of this document is to provide best practices and patterns to follow as well as illustrate the care needed in using WS-Policy to achieve the best possible results for interoperability. It is a complementary guide to using the specifications.
Editors
Asir Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp.
Web Services Policy Working Group- Family:
- Web Services Policy
Web Services Policy 1.5 - Primer is an introductory description of the Web Services Policy language. This document describes the policy language features using numerous examples. The associated Web Services Policy 1.5 - Framework and Web Services Policy 1.5 - Attachment specifications provide the complete normative description of the Web Services Policy language.
Editors
Asir Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp.
Web Services Policy Working Group- Family:
- Web Services Policy
This specification, Web Services Policy 1.5 - Attachment, defines two general-purpose mechanisms for associating policies, as defined in Web Services Policy 1.5 - Framework, with the subjects to which they apply. This specification also defines how these general-purpose mechanisms may be used to associate policies with WSDL and UDDI descriptions.
Editors
Asir Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp.
Web Services Policy Working Group- Family:
- Web Services Policy
The Web Services Policy 1.5 - Framework provides a general purpose model and corresponding syntax to describe the policies of entities in a Web services-based system.
Web Services Policy Framework defines a base set of constructs that can be used and extended by other Web services specifications to describe a broad range of service requirements and capabilities.
Editors
Asir Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp.
Web Services Policy Working Group- Family:
- Web Services Policy
GRDDL
Complete
GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. This GRDDL specification introduces markup based on existing standards for declaring that an XML document includes data compatible with the Resource Description Framework (RDF) and for linking to algorithms (typically represented in XSLT), for extracting this data from the document.
The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data.
A corresponding GRDDL Use Case Working Draft provides motivating examples. A GRDDL Primer demonstrates the mechanism on XHTML documents which include widely-deployed dialects known as microformats. A GRDDL Test Cases document illustrates specific issues in this design and provides materials to aid in test-driven development of GRDDL-aware agents.
Editors
Dan Connolly.
GRDDL Working Group- Family:
- GRDDL
This document describes and includes test cases for software agents that extract RDF from XML source documents by following the set of mechanisms outlined in the Gleaning Resource Description from Dialects of Language [GRDDL] specification. They demonstrate the expected behavior of a GRDDL-aware agent by specifying one (or more) RDF graph serializations which are the GRDDL results associated with a single source document.
Editors
Chimezie Ogbuji.
GRDDL Working Group- Family:
- GRDDL
GRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. It is a technique for obtaining RDF data from XML documents and in particular XHTML pages. Authors may explicitly associate documents with transformation algorithms, typically represented in XSLT, using a link element in the head of the document. Alternatively, the information needed to obtain the transformation may be held in an associated metadata profile document or namespace document. Clients reading the document can follow links across the Web using techniques described in the GRDDL specification to discover the appropriate transformations. This document uses a number of examples from the GRDDL Use Cases document to illustrate, in detail, the techniques GRDDL provides for associating documents with appropriate instructions for extracting any embedded data.
Editors
Harry Halpin, Ian Davis.
GRDDL Working Group- Family:
- GRDDL
Available in:
françaisGRDDL is a mechanism for Gleaning Resource Descriptions from Dialects of Languages. The GRDDL specification introduces markup for declaring that an XML document includes gleanable data and for linking to an algorithm, typically represented in XSLT, for gleaning the RDF data from the document.
The markup includes a namespace-qualified attribute for use in general-purpose XML documents and a profile-qualified link relationship for use in valid XHTML documents. The GRDDL mechanism also allows an XML namespace document (or XHTML profile document) to declare that every document associated with that namespace (or profile) includes gleanable data and for linking to an algorithm for gleaning the data.
A corresponding GRDDL specification provides complete technical details. A GRDDL Primer demonstrates the mechanism on XHTML documents which include widely-deployed dialects, more recently known as microformats.
Editors
Fabien Gandon.
GRDDL Working Group- Family:
- GRDDL
Available in:
françaisWeb Services Addressing
Complete
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - Metadata (this document) defines how the abstract properties defined in Web Services Addressing 1.0 - Core are described using WSDL, how to include WSDL metadata in endpoint references, and how WS-Policy can be used to indicate the support of WS-Addressing by a Web service.
Editors
Martin Gudgin, Marc Hadley, Tony Rogers, Ümit Yalçinalp.
Web Services Addressing Working Group- Family:
- Web Services Addressing
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - SOAP Binding (this document) defines the binding of the abstract properties defined in Web Services Addressing 1.0 - Core to SOAP Messages.
Editors
Martin Gudgin, Marc Hadley, Tony Rogers.
Web Services Addressing Working Group- Family:
- Web Services Addressing
Web Services Addressing provides transport-neutral mechanisms to address Web services and messages. Web Services Addressing 1.0 - Core (this document) defines a set of abstract properties and an XML Infoset [XML Information Set] representation thereof to reference Web services and to facilitate end-to-end addressing of endpoints in messages. This specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.
Editors
Martin Gudgin, Marc Hadley, Tony Rogers.
Web Services Addressing Working Group- Family:
- Web Services Addressing
WSDL
Complete
This document defines a set of extension attributes for the Web Services Description Language and XML Schema definition language that allows description of additional semantics of WSDL components. The specification defines how semantic annotation is accomplished using references to semantic models, e.g. ontologies. Semantic Annotations for WSDL and XML Schema (SAWSDL) does not specify a language for representing the semantic models. Instead it provides mechanisms by which concepts from the semantic models, typically defined outside the WSDL document, can be referenced from within WSDL and XML Schema components using annotations.
Editors
Joel Farrell, Holger Lausen.
Semantic Annotations for Web Services Description Language Working Group- Family:
- WSDL
Web services provide a standards-based foundation for exchanging information between ../distributed software systems. The W3C Recommendation Web Services Description Language (WSDL) specifies a standard way to describe the interfaces of a Web Service at a syntactic level and how to invoke it. While the syntactic descriptions provide information about the structure of input and output messages of an interface and about how to invoke the service, semantics are needed to describe what a Web service actual does. These semantics, when expressed in formal languages, disambiguate the description of Web services interfaces, paving the way for automatic discovery, composition and integration of software components. WSDL does not explicitly provide mechanisms to specify the semantics of a Web service. Semantic Annotations for WSDL and XML Schema (SAWSDL) defines mechanisms by which semantic annotations can be added to WSDL components. This usage guide is an accompanying document to SAWSDL specification. It presents examples illustrating how to associate semantic annotations with a Web service. These annotations could be used for classifying, discovering, matching, composing, and invoking Web services.
Some of the examples illustrated in this document use RDF and OWL Web Ontology Language for representing ontologies. Some knowledge of RDF and OWL is useful for understanding this document, but not essential.
Editors
Rama Akkiraju, Brahmananda Sapkota.
Semantic Annotations for Web Services Description Language Working Group- Family:
- WSDL
WSDL 1.1 Element Identifiers defines a syntax to identify individual elements in a WSDL 1.1 document.
Editors
David Orchard, Asir Vedamuthu, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp.
Web Services Policy Working Group- Family:
- WSDL
WSDL 2.0 is the Web Services Description Language, an XML language for describing Web services. This document, "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts", specifies predefined extensions for use in WSDL 2.0:
-
Message exchange patterns
-
Operation safety
-
Operation styles
-
Binding extensions for SOAP and HTTP
Editors
Roberto Chinnici, Hugo Haas, Amelia Lewis, Jean-Jacques Moreau, David Orchard, Sanjiva Weerawarana.
Web Services Description Working Group- Family:
- WSDL
Available in:
françaisThis specification defines additional message exchange patterns (MEPs) to be used in WSDL 2.0 and are provided as examples of the extensibility of WSDL 2.0.
Editors
Amelia Lewis.
Web Services Description Working Group- Family:
- WSDL
This document describes the Web Services Description Language Version 2.0 (WSDL 2.0), an XML language for describing Web services. This specification defines the core language which can be used to describe Web services based on an abstract model of what the service offers. It also defines the conformance criteria for documents in this language.
Editors
Roberto Chinnici, Jean-Jacques Moreau, Arthur Ryman, Sanjiva Weerawarana.
Web Services Description Working Group- Family:
- WSDL
Available in:
françaisThis document is a companion to the WSDL 2.0 specification (Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language [WSDL 2.0 Core], Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts [WSDL 2.0 Adjuncts]). It is intended for readers who wish to have an easier, less technical introduction to the main features of the language.
This primer is only intended to be a starting point toward use of WSDL 2.0, and hence does not describe every feature of the language. Users are expected to consult the WSDL 2.0 specification if they wish to make use of more sophisticated features or techniques.
Finally, this primer is non-normative. Any specific questions of what WSDL 2.0 requires or forbids should be referred to the WSDL 2.0 specification.
Editors
David Booth, Kevin Liu.
Web Services Description Working Group- Family:
- WSDL
Web Services Description Language (WSDL) provides a model and an XML format for describing Web services. This document describes a representation of that model in the Resource Description Language (RDF) and in the Web Ontology Language (OWL), and a mapping procedure for transforming particular WSDL descriptions into their RDF form.
Editors
Jacek Kopecky.
Web Services Description Working Group- Family:
- WSDL
WSDL SOAP 1.1 Binding describes the concrete details for using WSDL 2.0 in conjunction with SOAP 1.1 [SOAP11] protocol.
Editors
Asir Vedamuthu.
Web Services Description Working Group- Family:
- WSDL
This document captures the result of discussions by the Web Services Description Working Group regarding WSDL 2.0 type system extensibilty at the time of its publication. The Working Group normatively defines the use of XML Schema 1.0 as a type system in the WSDL 2.0 Core specification. This document sketches out the basics of extensions for Document Type Definitions (DTDs) and Relax NG.
Editors
Amelia Lewis, Bijan Parsia.
Web Services Description Working Group- Family:
- WSDL
Available in:
polskiSISR
Complete
Editors
Luc Van Tichelen, David Burke.
Voice Browser Working Group- Family:
- SISR
Device Independence
Complete
This document describes the set of properties that characterizes the capabilities of the device, the preferences of the user and other aspects of the context into which a Web page is to be delivered, known as the delivery context, and explores how to detect and make use of that context.
Editors
Roger Gimson, Rhys Lewis, Sailesh Sathish.
Device Independence Working Group- Family:
- Device Independence
The document provides a summary of several techniques and best practices that Web authors can employ when creating and delivering content to a diverse set of devices.
Editors
Rotan Hanrahan, Roland Merrick.
Device Independence Working Group- Family:
- Device Independence
This document offers principles that can lead towards the achievement of greater device independence for Web content and applications.
Editors
Roger Gimson.
Device Independence Working Group- Family:
- Device Independence
This document discusses the challenges that authors commonly face when building web content and applications that can be accessed by users via a wide variety of different devices with different capabilities.
Editors
Rhys Lewis.
Device Independence Working Group- Family:
- Device Independence
WICD
Complete
This document describes the use cases for a framework that combines documents by reference and the set of requirements for such a framework.
Editors
Daniel Appelquist, Timur Mehrvarz, Antoine Quint.
Compound Document Formats Working Group- Family:
- WICD
In progress
This document describes the use cases for a framework that combines documents and the set of requirements for such a framework.
Editors
Steve Speicher, Petri Vuorimaa.
Compound Document Formats Working Group- Family:
- WICD
SRGS
Complete
Editors
Andrew Hunt, Scott McGlashan.
Voice Browser Working Group- Family:
- SRGS
Available in:
françaisCC/PP
Complete
This document describes CC/PP (Composite Capabilities/Preference Profiles) structure and vocabularies. A CC/PP profile is a description of device capabilities and user preferences. This is often referred to as a device's delivery context and can be used to guide the adaptation of content presented to that device.
The Resource Description Framework (RDF) is used to create profiles that describe user agent capabilities and preferences. The structure of a profile is discussed. Topics include:
- structure of client capability and preference descriptions, AND
- use of RDF classes to ../distinguish different elements of a profile, so that a schema-aware RDF processor can handle CC/PP profiles embedded in other XML document types.
CC/PP vocabulary is identifiers (URIs) used to refer to specific capabilities and preferences, and covers:
- the types of values to which CC/PP attributes may refer,
- an appendix describing how to introduce new vocabularies,
- an appendix giving an example small client vocabulary covering print and display capabilities, and
- an appendix providing a survey of existing work from which new vocabularies may be derived.
Editors
Graham Klyne, Franklin Reynolds, Christopher Woodrow, Hidetaka Ohto, Johan Hjelm, Mark Butler, Luu Tran.
Device Independence Working Group- Family:
- CC/PP
Available in:
françaisThis document describes how existing vocabularies for different classes of devices and user agents can be used in CC/PP components, and how to create schemas that encapsulate existing vocabularies. It discusses the results of the coordination with the IETF CONNEG Working Group, as well as the WAP Forum UAPROF Working Group and several other groups, which have related activities. It contains a number of schemas and software examples which has been contributed voluntarily by individuals.
It also gives an example of heuristics, which can be used to adapt content to a CC/PP profile, thus giving some guidelines for those who want to use CC/PP to implement content adaptation. It also serves to provide vocabulary and schema designers with key guidelines regarding extensions to existing vocabularies or development of new ones.
Editors
Johan Hjelm, Lalitha Suryanarayana.
CC/PP Working Group- Family:
- CC/PP
Editors
Franklin Reynolds, Johan Hjelm, Spencer Dawkins, Sandeep Singhal.
UNKNOWN WORKING GROUP- Family:
- CC/PP
LBase: Semantics for Languages of the Semantic Web
Complete
This document describes a mechanism for providing a precise semantics for the Semantic Web Languages (referred to as SWELs from now on. The purpose of this is to define clearly the consequences and allowed inferences from constructs in these languages.
Editors
Ramanathan Guha, Patrick Hayes.
RDF Core Working Group- Family:
- LBase: Semantics for Languages of the Semantic Web
Xpointer
Complete
The XPointer xmlns() scheme is intended to be used with the XPointer Framework [XPtrFrame] to allow correct interpretation of namespace prefixes in pointers, for instance, namespace-qualified scheme names and namespace-qualified element or attribute names appearing within scheme data.
Editors
Steven DeRose, Ron Daniel, Eve Maler, Jonathan Marsh.
XML Linking Working Group- Family:
- Xpointer
This specification defines the XML Pointer Language (XPointer) Framework, an extensible system for XML addressing that underlies additional XPointer scheme specifications. The framework is intended to be used as a basis for fragment identifiers for any resource whose Internet media type is one of text/xml, application/xml, text/xml-external-parsed-entity, or application/xml-external-parsed-entity. Other XML-based media types are also encouraged to use this framework in defining their own fragment identifier languages.
Editors
Paul Grosso, Eve Maler, Jonathan Marsh, Norman Walsh.
XML Linking Working Group- Family:
- Xpointer
Available in:
françaisThe XPointer element() scheme is intended to be used with the XPointer Framework [XPtrFrame] to allow basic addressing of XML elements.
Editors
Paul Grosso, Eve Maler, Jonathan Marsh, Norman Walsh.
XML Linking Working Group- Family:
- Xpointer
Available in:
françaisEditors
Steven DeRose.
XML Linking Working Group- Family:
- Xpointer
Editors
Steven DeRose.
XML Linking Working Group- Family:
- Xpointer
XML Accessibility Guidelines
In progress
Requirements intended to be used for development of WCAG 2.0 Techniques, superceded by later plans.
Editors
Daniel Dardailler, Sean Palmer, Charles McCathieNevile.
Protocols and Formats Working Group- Family:
- XML Accessibility Guidelines
P3P
Complete
Editors
Joseph Reagle.
UNKNOWN WORKING GROUP- Family:
- P3P
Available in:
日本語TV Broadcast URI Schemes Requirements
Complete
This document is an informational document and discusses the requirements posed to URI schemes for identifying resources in Television (TV) Broadcast environments. The document is the outcome of discussions on this subject by the W3C TV-Web Interest Group [TVWebIG, TVWebMail].
Typical use cases are summarized where TV Broadcast URIs are involved. A ../distinction is made between Global and Local usage. Also, a hierarchy of resource types is identified. Requirements related to the Global usage case are listed.
Editors
Warner ten Kate.
UNKNOWN WORKING GROUP- Family:
- TV Broadcast URI Schemes Requirements